| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issues with Collector Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| Willtodd |
 Posted: Wed Sep 14, 2011 6:10 am Post subject: Issues with Collector Node |
 |
|
Newbie
Joined: 11 Apr 2009
Posts: 6
|
Issues with Collector Node
I have started using the Collector Node in one of my projects. I find it to be an excellent feature, however I'm noticing a couple of significant issues with it.
First, it does not appear to preserve the Environment. I have items stored in the Environment tree on my message prior to the Collector Node, but after the Collector Node, the Environment is dropped.
Second, occasionally the Collector Node names the folders under the Collection tree incorrectly. Suppose I have the node wired with two Input Terminals, named InA and InB. The Collector normally receives a Collection that looks like this:
| Code: |
InputRoot
Collection
InA
XMLNSC
MsgA
InB
XMLNSC
MsgB |
...but sometimes I get this:
| Code: |
InputRoot
Collection
InA
XMLNSC
MsgA
InA <!-- should be InB -->
XMLNSC
MsgB <!-- correct --> |
(This usually occurs after a deployment of some minor change to the flow and often persists until I restart the broker and queue manager.)
Clearly this is not a matter of MsgA arriving twice, because you'll note that although MsgA and MsgB arrive, both are labeled with InA. Since the nodes wired to the InA path are not capable of creatng a MsgB, this is clearly logically impossible, and seems to be a defect.
Has anyone else observed these behaviors? I am using Broker 7.0.0.1. I see that there have been some fixes to the Collector Node in 7.0.0.3, but I don't see any fixes that seem to address these issues specifically.
Thanks,
Todd |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Sep 14, 2011 6:17 am Post subject: Re: Issues with Collector Node |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Willtodd wrote: |
| Has anyone else observed these behaviors? |
No, but I've not had occassion to preserve the Environment across a Collector.
| Willtodd wrote: |
| I see that there have been some fixes to the Collector Node in 7.0.0.3, but I don't see any fixes that seem to address these issues specifically. |
It's probably worth applying the maintenance anyway. If nothing else it'll save a step when you raise the PMR.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 14, 2011 6:42 am Post subject: Re: Issues with Collector Node |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Willtodd wrote: |
| First, it does not appear to preserve the Environment. I have items stored in the Environment tree on my message prior to the Collector Node, but after the Collector Node, the Environment is dropped. |
Neither does an MQOutput node.
Collector node has *two* sides, and each side is a *different* message flow instance. If you want to keep Environment values, serialize them and stick them in a message and Collect that.
| Willtodd wrote: |
| Second, occasionally the Collector Node names the folders under the Collection tree incorrectly. |
This is more likely the way you are constructing the messages you pass into collector. Take a user trace or put Trace nodes before each In terminal. Confirm that you are really seeing an issue between the in terminal and the out terminal.
If so, open a PMR. |
|
| 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
|
|
|
|
