| Author |
Message
|
| extrany |
 Posted: Thu Sep 01, 2011 5:21 am Post subject: Error with promoting |
 |
|
Novice
Joined: 01 Sep 2011
Posts: 14
|
Hello All,
We have a big message flow (~ 70 subflows with different properties).
Some properties are promoted from subflows to main flow (DB data sources, schemas, tables and others).
We deploy this message flow and test it. Then we caught some DB errors. It happens because of wrong properties ( in 4 places: empty or simply another name of tables or schemas). Project -> Clean sometimes helps, sometimes not. In main flow (and in the bar file) the properties are correct. When i go to debug and see properties in compute node (in variables) i see incorrect values of table name or schema name.
The same subflows are used in other flows and we have no problem. In the flow (where we have problem) these subflows are used in many places.
Do you have any ideas? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Sep 01, 2011 5:23 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Does a User Trace show the same inconsistencies? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 01, 2011 5:24 am Post subject: Re: Error with promoting |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| extrany wrote: |
| Do you have any ideas? |
Why such a big flow? Why not break it up?
What version of WMB & Toolkit are you using?
How many projects are the flows split across?
How much memory does the machine building the bar file have?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| extrany |
| Posted: Thu Sep 01, 2011 6:11 am Post subject: |
|
|
Novice
Joined: 01 Sep 2011
Posts: 14
|
| Quote: |
| Does a User Trace show the same inconsistencies? |
Yes, the same... And we can see exception list without debugging (some logging to DB).
| Quote: |
Why such a big flow? Why not break it up?
What version of WMB & Toolkit are you using?
How many projects are the flows split across?
How much memory does the machine building the bar file have? |
It's not my design of the project 
Toolkit v. 6.1.0.9 and WMB v.6.1.0.5.
The main flow uses some msets (3 projects) and subflows in other 2 projects.
The machine has 2GB of memory. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Sep 01, 2011 6:16 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| extrany wrote: |
Toolkit v. 6.1.0.9 and WMB v.6.1.0.5.
|
Hmmm....
Perhaps that is your problem. I know that we had some issues with building .bar files on 6.1.0.9 and deploying them onto 6.1.0.3 so we kept a PC with 6.1.0.3 Toolkit on it for building some flows. This resolved the prolbem.
Now we are 6.1.0.9 all round so the pc with 6.1.0.3 on it is redundant.
I'd be ok with a 6.1.0.9 runtime and a 6.1.0.5 toolkit but not the other way round.
Have you tried building the problem flow with a 6.1.0.5 toolkit?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| extrany |
| Posted: Thu Sep 01, 2011 6:18 am Post subject: |
|
|
Novice
Joined: 01 Sep 2011
Posts: 14
|
| smdavies99 wrote: |
| extrany wrote: |
Toolkit v. 6.1.0.9 and WMB v.6.1.0.5.
|
Hmmm....
Perhaps that is your problem. I know that we had some issues with building .bar files on 6.1.0.9 and deploying them onto 6.1.0.3 so we kept a PC with 6.1.0.3 Toolkit on it for building some flows. This resolved the prolbem.
Now we are 6.1.0.9 all round so the pc with 6.1.0.3 on it is redundant.
I'd be ok with a 6.1.0.9 runtime and a 6.1.0.5 toolkit but not the other way round.
Have you tried building the problem flow with a 6.1.0.5 toolkit? |
Yes, i had toolkit v. 6.1.0.5 and i upgraded it because of this error, but it didn't help me. |
|
| Back to top |
|
|
| extrany |
| Posted: Thu Sep 01, 2011 6:24 am Post subject: |
|
|
Novice
Joined: 01 Sep 2011
Posts: 14
|
| Now i hardcoded the problem values in compute nodes (schemas, tables) and all is ok, but it is not the solution |
|
| Back to top |
|
|
| Herbert |
| Posted: Thu Sep 01, 2011 6:43 am Post subject: |
|
|
Centurion
Joined: 05 Dec 2006
Posts: 146
Location: Leersum, The Netherlands
|
| extrany wrote: |
| Now i hardcoded the problem values in compute nodes (schemas, tables) and all is ok, but it is not the solution |
I can confirm then when using the same subflow multiple times in a main flow with different values for promoted properties, this happens sometimes.
I found it a nice hint to do a re-design  The part that was used many times is now behind a own queue. |
|
| Back to top |
|
|
|
|
