| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SOLVED: MQOutput Node cannot commit Message to Queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| kerbling |
 Posted: Wed Mar 28, 2007 1:01 am Post subject: SOLVED: MQOutput Node cannot commit Message to Queue |
 |
|
Novice
Joined: 15 Aug 2005
Posts: 10
|
Hello,
We have several UNIX environments (Sun Solaris). I have a logging flow. The message is written to an Oracle DB the put to a local output queue (OUTQ).
On ENVA it works.
On ENVB the message appears to be put to the OUTQ, the curdepth goes to 1. However, it is not possible to get message from OUTQ. The application says the queue is empty. Furthermore, subsequent messages to the logging flow back up on the input queue. Essentially suggesting that the original message has not committed.
The versions of MQ and WBIMB are the same on ENVA and ENVB. The defenitions of the queues are all the same. The code is the same that is deployed to the brokers on ENVA and ENVB.
Any ideas? This is quite urgent!
Last edited by kerbling on Wed Mar 28, 2007 2:52 am; edited 1 time in total |
|
| Back to top |
|
 |
| vk |
| Posted: Wed Mar 28, 2007 1:06 am Post subject: |
|
|
Partisan
Joined: 20 Sep 2005
Posts: 302
Location: Houston
|
Check if there is sufficient MQ file system space. It MQ file system is full, then the messages cannot be committed.
Did you try running an mqsichangetrace? This will show you what happened at the output node.
Regards,
VK. |
|
| Back to top |
|
|
| kerbling |
| Posted: Wed Mar 28, 2007 2:00 am Post subject: |
|
|
Novice
Joined: 15 Aug 2005
Posts: 10
|
Thanks for the quick response. Sorry I should have mentioned that I had run mqsichangetrace at debug to assess what the flow was doing. There were no errors and finally the trace says that is connects to the OUTQ and puts OK.
BIP4124I: Message propagated to 'out' terminal of compute node 'MyFlow'.
BIP2638I: The MQ output node 'MyFlow' attempted to write a message to queue 'OUTQ' connected to queue manager ''. The MQCC was '0' and the MQRC was '0'.
BIP2622I: Message successfully output by output node 'MyFlow' to queue 'OUTQ' on queue manager ''.
This is what is so strange!
Also, /var/mqm is only at 11% ... so there is plenty of space. |
|
| Back to top |
|
|
| kerbling |
| Posted: Wed Mar 28, 2007 2:20 am Post subject: SOLVED: MQOutput Node cannot commit Message to Queue |
|
|
Novice
Joined: 15 Aug 2005
Posts: 10
|
We just bounced the Oracle DB that the Broker was logging to and now there is not problem.
Unfortunately, we were unable to get any trace from the DB before it wsas bounced so cannot determine exactly what was causing the problem.
However, it is obvious that the transaction between the Broker and the Oracle DB was not right. Probably the Broker could not complete it's communication with the DB and therefore could not commit the message to the queue; although it wanted to! |
|
| 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
|
|
|
|
