jQuery in Action, 2nd edition*
The moose likes Websphere and the fly likes MQ: MQException: Completion Code 2, Reason 2033 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "MQ: MQException: Completion Code 2, Reason 2033" Watch "MQ: MQException: Completion Code 2, Reason 2033" New topic
Author

MQ: MQException: Completion Code 2, Reason 2033

Vadim Prudnikov
Greenhorn

Joined: Jul 06, 2006
Posts: 2
Hi. Can you help me with the problem?
I create MQQueueManager, send message and try to receive.
Exception occurs on a message receiving (MQQueue.get).

This is a code parts (i don't show exception catching):


queue.get(message, gmo); throws an exception.
Help please what parameters are wrong?
Many Thanks.
Jesus Angeles
Ranch Hand

Joined: Feb 26, 2005
Posts: 2053
One possible reason for 2033 is timeout.
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18541
    
    8

"Vad Pr", could you please review the JavaRanch name policy? In particular it says you must use a real name as your display name. You can change your display name here. Thank you for your cooperation.
Vadim Prudnikov
Greenhorn

Joined: Jul 06, 2006
Posts: 2
with waitInterval = 100000... does not work.
I think the problem is not in timeout.

Any other ideas?
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18541
    
    8

I googled for that error message and found another answer on a different mailing list. It may or may not apply to your situation.
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18541
    
    8

And then there's this answer from this very forum 2 1/2 years ago.
Yogesh Gandhi
Ranch Hand

Joined: Dec 05, 2008
Posts: 212
I am also facing the similar problem.

I have written two more functions:



Only difference in the two functions is that queueName is being changed.
But I get a message 2033 when reading from Enquiry Queue, while the same code works perfectly fine in case of Request Queue.

Can anyone give me a clue, what could be the possible reason for such a behavior.


The function readMQMessage uses the following options:



 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: MQ: MQException: Completion Code 2, Reason 2033