ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » Reason code 2033 when reading a message from 2nd input queue

Post new topic  Reply to topic
 Reason code 2033 when reading a message from 2nd input queue « View previous topic :: View next topic » 
Author Message
DSPS
PostPosted: Mon Sep 15, 2008 4:04 am    Post subject: Reason code 2033 when reading a message from 2nd input queue Reply with quote

Apprentice

Joined: 11 Sep 2008
Posts: 44
Location: Southern England

I have an application, stand-alone Java class which is intended to open two input queues and one output queue, all within one queue manager.

It reads one message from the first input queue, writes it to the output queue, reads a message from the second input queue and writes that to the output queue as well. It is meant to carry on until the end of one of the input queues, or until a particular number of messages have been copied to the output queue from each input.

Trouble is, whether I use MQGMO_BROWSE_FIRST or MQGMO_BROWSE_NEXT for the message options for the first read off the second queue, I get a reason code 2033 and the application exits. (Regardless of which input I open first, and which one I open second)

Both input queues have a depth (27834 and 8465 messages respectively) but I'm being told which ever one I open second gets to the end.

If I cheat and give it the same input queue name for both input queues, it works fine, and processes the requested number of messages off the queue.

Very odd. I suspect it's something to do with my options on the queue, but I'm not sure what.

Any help gratefully accepted.

Peter.
_________________
Distributed Systems Professional Services
WebSphere and MQ Consulting and Training
Back to top
View user's profile Send private message Visit poster's website
Tibor
PostPosted: Tue Sep 16, 2008 2:03 am    Post subject: Reply with quote

Grand Master

Joined: 20 May 2001
Posts: 1033
Location: Hungary

Peter, do you use a different object instances for getting messages (GetMessageOptions, Queue, etc.)? And what about the transaction management? Did you commit your messages?

Tibor
Back to top
View user's profile Send private message
zpat
PostPosted: Tue Sep 16, 2008 2:35 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

MQRC 2033 does not always mean end of queue, it means No Message Available matching your selection criteria (which you may not have intended).

Try setting the MQMD msgid and correlid fields to NONE after the MQPUT and before the next MQGET.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » Reason code 2033 when reading a message from 2nd input queue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.