| Author |
Message
|
| cutejigs |
 Posted: Sun Jan 06, 2013 10:57 pm Post subject: WMB8 message is suddenly vanishing |
 |
|
Novice
Joined: 20 Jan 2010
Posts: 20
|
hi.
i started using Websphere Message Broker 8 and notice that whenever i use subflows, the message i sent completely vanish on some nodes. as an example:
Processing MainFlow:
MQSource subflow -> other processing subflow
MQSource Subflow:
MQInput node -> Log subflow -> Output node
Log subflow
Input node -> Try/Catch node -> Compute node -> MQOutput node -> Output node
The Processing Main Flow is an Application while the MQSource and Log subflows belong to a Library. The MQSource and Log subflows works fine if it is a "Message Flow" but when I convert it to a subflow, the messages vanishes at the Try/Catch node (i use Debug mode to see this)
is there anyone encountering the same problem?
thanks. |
|
| Back to top |
|
 |
| rekarm01 |
| Posted: Sun Jan 06, 2013 11:43 pm Post subject: Re: WMB8 message is suddenly vanishing |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
This is probably related to similar issues, here and here; the broker does not create all of the necessary connections for nested subflows, or for input/output nodes with multiple connections.
A fix is planned for v8.0.0.2. Workarounds include flattening nested subflows, limiting the number of connections to one per input/output node, converting subflow projects to msgflow projects, or compiling subflows in-line. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Jan 07, 2013 6:04 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| cutejigs |
| Posted: Mon Jan 07, 2013 3:00 pm Post subject: |
|
|
Novice
Joined: 20 Jan 2010
Posts: 20
|
@rekarm01 thanks for that info, really help a lot! 
will report this back to the architect and admin to wait for the next fix pack.
btw, could you specify how to do the workaround 1. flattening nested subflows 2. compiling subflows in line?
@lancelotlinc i also tried this one
 |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Wed Jan 09, 2013 11:16 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| cutejigs wrote: |
| btw, could you specify how to do the workaround 1. flattening nested subflows 2. compiling subflows in line? |
1. Maybe there's a better word for that, but "flattening" nested subflows means don't have one subflow call another - delete some subflows, and move their functionality to other flows. For example:
| Quote: |
Processing MainFlow:
MQInput node -> Log subflow -> other processing subflow
Log subflow:
Input node -> Try/Catch node -> Compute node -> MQOutput node -> Output node |
2. When compiling a barfile, there's a checkbox to "Compile and in-line" resources. |
|
| Back to top |
|
|
| cutejigs |
| Posted: Tue Jan 15, 2013 9:20 pm Post subject: |
|
|
Novice
Joined: 20 Jan 2010
Posts: 20
|
| thanks rekarm01! i will try that solution, hopefully the architect will agree to wait for the fix pack |
|
| Back to top |
|
|
|
|
