| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error Code 2039 -- queue not open for output |
« View previous topic :: View next topic » |
| Author |
Message
|
| ajf84c |
 Posted: Wed May 14, 2003 6:08 am Post subject: Error Code 2039 -- queue not open for output |
 |
|
Newbie
Joined: 14 May 2003
Posts: 2
|
We are setting the open options using MQOO_OUTPUT
+ MQOO_FAIL_IF_QUIESCING.
Our Order application calls this small utility to place messages on a queue. We send well over 18,000 messages a day which means this utility is called over 18,000 times. Every blue moon (approx 1 a month) we get this 2039 error (queue not open for output). We clearly are setting this option before we open the queue. In addition, shouldn't every call fail if we didn't open the queue for output.
Our utility is written in C and it runs on HP-UX version 11.0. We are currently on version 5.2 of MQSeries.
Any help would be appreciated.
Thanks.
_________________
Alan Flowers
Sherwin Williams Company |
|
| Back to top |
|
 |
| bduncan |
| Posted: Wed May 14, 2003 11:16 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
It sounds like your utility is being executed every time you need to put a message, and then it exits. Why is this? Can't the utility be a long running application which keeps the queue open and puts messages to it as necessary?
Also, are you putting these messages to a local queue, or a remote queue definition? And what is picking the messages up?
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| JohnMN |
| Posted: Wed May 14, 2003 11:58 am Post subject: |
|
|
Novice
Joined: 26 Feb 2003
Posts: 19
|
| Are you also testing the RC after the MQOPEN? Perhaps it is the MQOPEN that is failing once in a blue moon. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed May 14, 2003 1:49 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| This could be APAR IY31882 which is fixed in MQ 5.2 CSD6. Do you have the latest CSD applied? |
|
| Back to top |
|
|
| ajf84c |
| Posted: Mon Jun 09, 2003 9:28 am Post subject: |
|
|
Newbie
Joined: 14 May 2003
Posts: 2
|
Thanks Everyone...
Brandon, The application that calls this utility is an Order Management System. There are built in scripts that are invoked by an event received from the user interface that calls this utility and passes an xml message and an INI file (which contains the remote queue to write to) as arguments. We are not able to run a continous process which just opens one queue as the remote destination (which queue to write to) depends on the event.
We are currently on CSD5 but I believe we are planning to move to 5.3 soon.
For a temporary fix we just resubmit any failed messages at most 5 times within a 30 second period. We have not seen any problems after implementing this workaround. Hopefully moving to 5.3 (which will contain CSD6) will fix the problem without this workaround.
Again, thanks to everyone!
_________________
Alan Flowers
Sherwin Williams Company |
|
| 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
|
|
|
|
