| Author |
Message
|
| satyasheel15 |
 Posted: Wed Jun 09, 2004 8:45 am Post subject: Message Flow Error |
 |
|
Voyager
Joined: 04 Mar 2003
Posts: 86
|
I have created one CWF Message Set and in the input node, I am setting the properties of the input node to the CWF message defined.
But when I put the test message, I am getting the following error.
Timestamps are formatted in local time, 300 minutes before GMT.
2004-06-09 11:36:33.414604 5141 UserTrace BIP4040I: The Execution Group 'satyasheel' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-06-09 11:36:33.415168 5141 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-09 11:36:33.415184 5141 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0260'.
2004-06-09 11:38:13.449298 5141 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-06-09 11:38:13.449420 5141 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-09 11:38:13.449465 5141 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-09 11:38:13.449742 5141 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '234' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
Threads encountered in this trace:
5141
Please advise. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Wed Jun 09, 2004 9:21 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| I am getting the following error |
What error ?
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| satyasheel15 |
| Posted: Wed Jun 09, 2004 12:56 pm Post subject: |
|
|
Voyager
Joined: 04 Mar 2003
Posts: 86
|
I am getting the following error in the trace file when I am doing the flow level debug :
2004-06-09 11:36:33.414604 5141 UserTrace BIP4040I: The Execution Group 'satyasheel' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-06-09 11:36:33.415168 5141 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-09 11:36:33.415184 5141 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0260'.
2004-06-09 11:38:13.449298 5141 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-06-09 11:38:13.449420 5141 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-09 11:38:13.449465 5141 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-09 11:38:13.449742 5141 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '234' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 09, 2004 1:10 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| satyasheel15 wrote: |
| I am getting the following error in the trace file when I am doing the flow level debug : |
The tracing you are posting does not indicate an error.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jun 09, 2004 10:37 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I don't think your user trace is turned on correctly. Please make sure you run the mqsichangetrace command correctly or use Control Center to turn-on the trace for your Message Flow/EG.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
