|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
IIB9: Collector Node in Subflows |
« View previous topic :: View next topic » |
Author |
Message
|
aabdi |
Posted: Thu Oct 01, 2015 8:31 am Post subject: IIB9: Collector Node in Subflows |
|
|
Newbie
Joined: 01 Oct 2015 Posts: 2
|
Hallo all,
I'm not very familiar with collector node. I'm using it placed into subflow. I have to make different collections always with same X-Path so this was a good use case to place a collector node into a subflow. Collection name was propagated.
This subflow was integrated into four main flows.
Issue is that messages collected from one main flow are preceded into another main flow after collector node. For me seams this like a bug.
I can't find any information which collector property has to be unique to avoid this issue.
Workaround is to move collector node into main flows so I have to specify it for four times.
Do I make same mistakes or is collector node not subflow able in IIB9?
Thanks for answers,
With regards,
aabdi |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Oct 01, 2015 8:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
The output terminal of Collector starts a new instance of the message flow, as if it were an Input node.
So you can't do anything to configure the Collector node to return to the same instance of the message flow that provided the input.
If you want to do that, you have to use Aggregation instead of Collection. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
aabdi |
Posted: Fri Oct 02, 2015 6:19 am Post subject: |
|
|
Newbie
Joined: 01 Oct 2015 Posts: 2
|
Hi mqjeff,
You wrote:
Quote: |
The output terminal of Collector starts a new instance of the message flow, as if it were an Input node. |
This is correct and requiried. It should be an new Instance but a new instance of same message flow.
Bug is that Collector starts a new instance of the ANOTHER message flow. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Oct 02, 2015 6:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
aabdi wrote: |
Hi mqjeff,
You wrote:
Quote: |
The output terminal of Collector starts a new instance of the message flow, as if it were an Input node. |
This is correct and requiried. It should be an new Instance but a new instance of same message flow.
Bug is that Collector starts a new instance of the ANOTHER message flow. |
...
Ok. So you have the same subflow in more than one message flow, and the collector node pushes it's output into a random message flow that is using that subflow.
Try using a different Collector configurable service for each flow. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|