| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| queue.get() suddenly returns 2033 |
« View previous topic :: View next topic » |
| Author |
Message
|
| jehm |
 Posted: Thu Dec 02, 2004 1:00 am Post subject: queue.get() suddenly returns 2033 |
 |
|
Newbie
Joined: 02 Dec 2004
Posts: 2
Location: Norway
|
Hi!
Newbie question:
I've made a MQ-client program that puts a message to a queue, and waits for a result response from another queue. After about 7000 iterations of this (should be 10000 total), my queue.put() still works fine, but my queue.get() suddenly starts to return 2033 reasoncodes  . Any clue how I can figure out what the problem is? (I'm not able to check whats going on at the server side, but is it something I could ask the backend guys to check for?  )
atb
// Jon |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Thu Dec 02, 2004 6:26 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Double-check that the message actually got put to the queue and that they aren't stuck in an uncommitted unit of work. Make sure that somebody else hasn't started another application that is getting them instead of you. Also, what programming language are you using? |
|
| Back to top |
|
|
| csmith28 |
| Posted: Thu Dec 02, 2004 9:54 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
2033 X’07F1’ MQRC_NO_MSG_AVAILABLE
An MQGET call was issued, but there is no message on the queue satisfying the selection
criteria specified in MQMD (the MsgId and CorrelId fields), and in MQGMO (the Options and
MatchOptions fields). Either the MQGMO_WAIT option was not specified, or the time interval
specified by the WaitInterval field in MQGMO has expired. This reason is also returned for
an MQGET call for browse, when the end of the queue has been reached.
This reason code can also be returned by the mqGetBag and mqExecute calls. mqGetBag is
similar to MQGET. For the mqExecute call, the completion code can be either
MQCC_WARNING or MQCC_FAILED:
v If the completion code is MQCC_WARNING, some response messages were received
during the specified wait interval, but not all. The response bag contains system-generated
nested bags for the messages that were received.
v If the completion code is MQCC_FAILED, no response messages were received during the
specified wait interval.
Corrective action: If this is an expected condition, no corrective action is required.
If this is an unexpected condition, check that:
v The message was put on the queue successfully.
v The unit of work (if any) used for the MQPUT or MQPUT1 call was committed
successfully.
v The options controlling the selection criteria are specified correctly. All of the following can
affect the eligibility of a message for return on the MQGET call:
MQGMO_LOGICAL_ORDER
MQGMO_ALL_MSGS_AVAILABLE
MQGMO_ALL_SEGMENTS_AVAILABLE
MQGMO_COMPLETE_MSG
MQMO_MATCH_MSG_ID
MQMO_MATCH_CORREL_ID
MQMO_MATCH_GROUP_ID
MQMO_MATCH_MSG_SEQ_NUMBER
MQMO_MATCH_OFFSET
Value of MsgId field in MQMD
Value of CorrelId field in MQMD
Consider waiting longer for the message.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| jehm |
| Posted: Wed Dec 08, 2004 5:50 am Post subject: CorrelationId |
|
|
Newbie
Joined: 02 Dec 2004
Posts: 2
Location: Norway
|
| Seems like the backend guys started to put some strange stuff in the CorrelationId when the process had been running for some while (probably giving 2033 since I used setCorrelationId() on my getmsg). Anywayz...tnx guys! |
|
| 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
|
|
|
|
