| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Collector node |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sam Uppu |
 Posted: Tue Sep 28, 2010 2:45 pm Post subject: Collector node |
 |
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
Hi guys,
In my msgflow, I am setting environment variable. But I dont see environment variable after collector node. I need value in environment variable down the flow. Is it the behavior of collector node to remove environment variable? Pls throw some light on this . |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Sep 28, 2010 4:34 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Right, so.
Environment tree is always and only scoped to the specific instance of the message flow.
So if two messages come in to the same MQInput node, they will always have entirely separate Environment trees.
The In terminals of collector node are also separate instance of the "same" message flow.
So Environment tree does not convey.
Sorry.
You can construct an extra message, that goes to an extra "in" terminal of Collector, that holds the necessary Environment data.
But this assumes that the necessary Environment data is only required in the "first" message.
If you need collector to, for example, assemble all of the relevant data from every environment tree from *every* input message that goes to collector...
then this is more complicated, and you'll have to spend some time thinking. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Wed Sep 29, 2010 1:05 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| mqjeff wrote: |
Right, so.
Environment tree is always and only scoped to the specific instance of the message flow.
So if two messages come in to the same MQInput node, they will always have entirely separate Environment trees.
The In terminals of collector node are also separate instance of the "same" message flow.
So Environment tree does not convey.
Sorry.
You can construct an extra message, that goes to an extra "in" terminal of Collector, that holds the necessary Environment data.
But this assumes that the necessary Environment data is only required in the "first" message.
If you need collector to, for example, assemble all of the relevant data from every environment tree from *every* input message that goes to collector...
then this is more complicated, and you'll have to spend some time thinking. |
I am planning to use compute node instead of collector node. I have built a collector like structure in compute node and sending the message to WTX node. But I see below exception from Wtx node
| Quote: |
RecoverableException
File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbDataFlowNode.cpp
Line:INTEGER:957
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmCniNode
Name:CHARACTER:Test_collection#FCMComposite_1_4
Label:CHARACTER:Test_collection.WTX Map
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:CMqsiNode.cpp
Line:INTEGER:2662
Function:CHARACTER:cniElementAsBitstream
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:txmsgv82
Severity:INTEGER:3
Number:INTEGER:268370924
Text:CHARACTER:Exception
Insert
Type:INTEGER:5
Text:CHARACTER:cniElementAsBitstream
File:CHARACTER:CMqsiNode.cpp
Line:INTEGER:2662
Function:CHARACTER:cniElementAsBitstream
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:txmsgv82
Severity:INTEGER:3
Number:INTEGER:268370924
Text:CHARACTER:Exception
Insert
Type:INTEGER:5
Text:CHARACTER:cniElementAsBitstream
Type:INTEGER:5
Text:CHARACTER:cniElementAsBitstream |
Can you guys throw some light? |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Wed Sep 29, 2010 1:44 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
When I tured on User trace I see that parsing error occurs. Below is the message from user trace.
UserTrace BIP6068W: A request was made to serialize a bitstream from element ''BLOB'' using parser ''COLLECTION''. The result was zero bytes long.
The node or ESQL ASBITSTREAM function requested that an element serialize its bitstream and this resulted in no bytes being written.
If the output bitstream should not have been zero bytes long, ensure that the correct element was specified.
If the parser name is blank or set to a root parser, associate an owning parser with the element:
If created in ESQL, the DOMAIN clause of the CREATE statement can be used.
If created using the user-defined extension API use a method that allows a parser to be specified.
2010-09-29 16:39:11.577168 6128 UserTrace BIP4150E: User-defined extension input parameter failed debug validation check.
Input parameter 3 passed into function ''cniElementAsBitstream'' does not have a valid value.
Correct user-defined extension implementation accordingly.
2010-09-29 16:39:11.577264 6128 UserTrace BIP2231E: Error detected whilst processing a message in node 'Test_collection.WTX Map'.
The message broker detected an error whilst processing a message in node 'Test_collection.WTX Map'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2010-09-29 16:39:11.577275 6128 RecoverableException DTXMB1004E: WTX for WMB exception {1}:
'cniElementAsBitstream' |
|
| 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
|
|
|
|
