| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Getting Backedout in WMB 6.0 Message Flow Compute No |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ranodip Basu |
 Posted: Tue Oct 17, 2006 4:57 am Post subject: Message Getting Backedout in WMB 6.0 Message Flow Compute No |
 |
|
Apprentice
Joined: 23 Sep 2004
Posts: 48
|
Hi All,
We are using WMB 6.0(config mgr & toolkit installed in windows, broker in suse linux) and wmq 6.0(installed in suse linux). We have developed a message flow consisting of mq input,output & compute node which will take a message in tds format and convert to xml format. The problem is that the output message getting backed out. I have ran usertrace found no error within the message flow proccessing. The error message is as in below :
| Quote: |
2006-10-17 07:40:34.582870~79510704 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'MSG_FLOW1.TRANSFORM_XML'.
2006-10-17 07:40:35.585002~79510704 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'MSG_FLOW1.INPUT'.
Node 'MSG_FLOW1.INPUT' has received a message which has previously been backed out because of a processing error in the message flow. The MQMD 'backoutCount' of the message exceeds (or equals) the 'backoutThreshold' defined for the WebSphere MQ input queue. The message broker is propagating the message to the failure terminal of the node. |
I don't have much idea about these 'backoutCount' and 'backoutThreshold', but heard that it is arised due to problems in messageflow ESQL.
Could you please give any light on the probable causes for this error and what can be the done to solve it ?
Thanks,
Ranodip Basu |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Oct 17, 2006 5:02 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Ranodip Basu,
Take a file trace(Trace Node) of the output from the compute. Please paste that along with your code.
Regards. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 17, 2006 5:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There should be more errors in the log that tell you what's going on.
If you can't, or don't want to, modify the flow to include a Trace node that has "${ExceptionList}" in the pattern, then you can use User Trace at the Debug level to see what's going wrong.
You can read about using User Trace in the Info Center under Troubleshooting.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Ranodip Basu |
| Posted: Wed Oct 25, 2006 10:51 pm Post subject: |
|
|
Apprentice
Joined: 23 Sep 2004
Posts: 48
|
Thanks Elvis and Jefflowrey for your prompt repies. I am extremely sorry to replying you guys late. The problem has been solved.
Actually the errors I had posted before were from user trace. Also I have tried the trace node in message flow with both ${Root} and ${ExceptionList}.I have not found anything for exception list and the output message is fromed properly as showned for ${Root} in trace node between compute amd MQOutput node.
I have then recreated the message flow again along with some change in message set and found to become running fine.
Regards,
Ranodip |
|
| 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
|
|
|
|
