| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Output Node: Unable to put message |
View previous topic :: View next topic |
| Author |
Message
|
| miguelanselmo |
 Posted: Fri Feb 04, 2005 1:39 am Post subject: MQ Output Node: Unable to put message |
 |
|
Novice
Joined: 28 Oct 2003
Posts: 15
|
Hi all,
I have a problem with my message flow that at the end of them put a message in a queue but sometimes the message flow is not able to put the message on the queue. The message that the flow is putting normally is at most 200/300 Kb.
The error that i received is the following:
<Error><RecoverableException><File>F:\build\S210_BP\src\DataFlowEngine\ImbMqOutputNode.cpp</File><Line>727</Line><Function>ImbMqOutputNode::evaluate</Function><Type>ComIbmMQOutputNode</Type><Name>445475a1-f800-0000-0080-9938b3abff93</Name><Label>DELFOR_CAR.MQOut XML</Label><Text>Caught exception and rethrowing</Text><Catalog>WMQIv210</Catalog><Severity>3</Severity><Number>2230</Number><RecoverableException><File>F:\build\S210_BP\src\DataFlowEngine\ImbMqOutputNode.cpp</File><Line>1914</Line><Function>ImbMqOutputNode::putMessage</Function><Type>ComIbmMQOutputNode</Type><Name>445475a1-f800-0000-0080-9938b3abff93</Name><Label>DELFOR_CAR.MQOut XML</Label><Text>Unable to put message</Text><Catalog>WMQIv210</Catalog><Severity>3</Severity><Number>2620</Number><Insert><Type>5</Type><Text></Text></Insert><Insert><Type>5</Type><Text>WMQI_XML_OUT</Text></Insert><Insert><Type>2</Type><Text>2</Text></Insert><Insert><Type>2</Type><Text>2003</Text></Insert></RecoverableException></Recoverabl
eExcepti
on></Error>
Thanks for any help |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Fri Feb 04, 2005 4:29 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
The last code 2003 indicates a backout of the message,
something else in your message flow like a database node around?
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| miguelanselmo |
| Posted: Fri Feb 04, 2005 6:17 am Post subject: |
|
|
Novice
Joined: 28 Oct 2003
Posts: 15
|
Hi,
Yes, there are database node and compute node.
Another thing is that the input queue has the “Backout Threshold” with the value '3'. |
|
| Back to top |
|
|
| gyadavil |
| Posted: Fri Feb 04, 2005 11:00 pm Post subject: |
|
|
Acolyte
Joined: 01 Feb 2005
Posts: 62
|
| May be a stupic check, but check your output Queue Properties. What is the max depth in that and how many message you have. |
|
| Back to top |
|
|
| mqmhr |
| Posted: Fri Feb 04, 2005 11:43 pm Post subject: |
|
|
Centurion
Joined: 28 Dec 2004
Posts: 105
|
| Quote: |
2003 MQRC_BACKED_OUT X'7D3' Unit of work encountered fatal error or backed out.
This occurs in the following cases:
On an MQCMIT or MQDISC call, when the commit operation has failed and the unit of work has been backed out. All protected resources have been returned to their state at the start of the unit of work. The MQCMIT call returns completion code MQCC_FAILED; the MQDISC call returns completion code MQCC_WARNING.
On MVS/ESA, this reason code occurs only for batch applications.
On an MQGET, MQPUT, or MQPUT1 call that is operating within a unit of work, when the unit of work has already encountered an error that prevents the unit of work being committed (for example, when the log space is exhausted). The application must issue the appropriate call to back out the unit of work. For a unit of work coordinated by the queue manager, this call is the MQBACK call, although the MQCMIT call has the same effect in these circumstances.
On MVS/ESA this case does not occur.
On OS/400, this reason code does not occur.
Corrective action: Check the returns from previous calls to the queue manager. For example, a previous MQPUT call may have failed. |
Somewhere in your message flow, an error is occurring. This may be the database node or any other Node before the Output Node. Because of this error, the broker is not able to commit the UOW.
Check if all the nodes before the Output Node are behaving in the expected manner. Then you could check the properties of the MQ Output node and ensure that the queue name is valid, the queue is not full, you have sufficient authorities to put messages in the queue and so on. |
|
| 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
|
|
|
|
