| Author |
Message
|
| MQ_adi |
 Posted: Fri Apr 03, 2009 8:33 am Post subject: MQException 2033 |
 |
|
Novice
Joined: 03 Apr 2009
Posts: 13
|
Hi All,
We are using MQ to interact with a document engine. The interaction is -
1. we put an XML file in input queue
2. a document engine picks up this XML, creates pdf and puts the pdf in anotehr queue
3. we pick up the pdf from the output queue
The application server, MQ and document engine are in the same unix server. The whole set up was working fine but suddenly we started getting till we started getting 2033 error code. Below is the exception.
MQException trying to get document from the queue:MQJE001: Completio
n Code 2, Reason 2033
When I see the output queue, I could see the pdf; i even tried to get the pdf using a MQ client from my desktop and it was working fine.
When we setup the MQ and document engine in another unix, it's working fine.
What would be possible cause and solution of this error.
Regards,
Adi |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Apr 03, 2009 8:35 am Post subject: Re: MQException 2033 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| MQ_adi wrote: |
Hi All,
We are using MQ to interact with a document engine. The interaction is -
1. we put an XML file in input queue
2. a document engine picks up this XML, creates pdf and puts the pdf in anotehr queue
3. we pick up the pdf from the output queue
The application server, MQ and document engine are in the same unix server. The whole set up was working fine but suddenly we started getting till we started getting 2033 error code. Below is the exception.
MQException trying to get document from the queue:MQJE001: Completio
n Code 2, Reason 2033
When I see the output queue, I could see the pdf; i even tried to get the pdf using a MQ client from my desktop and it was working fine.
When we setup the MQ and document engine in another unix, it's working fine.
What would be possible cause and solution of this error.
Regards,
Adi |
check that the request message has been committed before you wait for the reply 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Fri Apr 03, 2009 8:37 am Post subject: Re: MQException 2033 |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| MQ_adi wrote: |
Hi All,
We are using MQ to interact with a document engine. The interaction is -
1. we put an XML file in input queue
2. a document engine picks up this XML, creates pdf and puts the pdf in anotehr queue
3. we pick up the pdf from the output queue
The application server, MQ and document engine are in the same unix server. The whole set up was working fine but suddenly we started getting till we started getting 2033 error code. Below is the exception.
MQException trying to get document from the queue:MQJE001: Completio
n Code 2, Reason 2033
When I see the output queue, I could see the pdf; i even tried to get the pdf using a MQ client from my desktop and it was working fine.
When we setup the MQ and document engine in another unix, it's working fine.
What would be possible cause and solution of this error.
Regards,
Adi |
From MQ perspective 2033 is MQRC_NO_MSG_AVAILABLE on the queue when you try to get it. Is anybody changed anything anywhere as it was working fine earlier.
Thanks. |
|
| Back to top |
|
|
| MQ_adi |
| Posted: Fri Apr 03, 2009 8:37 am Post subject: |
|
|
Novice
Joined: 03 Apr 2009
Posts: 13
|
Hi,
I think it - as the document is generated.
Thnx |
|
| Back to top |
|
|
| MQ_adi |
| Posted: Fri Apr 03, 2009 8:39 am Post subject: |
|
|
Novice
Joined: 03 Apr 2009
Posts: 13
|
Hi,
Re-changes - I am sure that there were no code changes.
Thnx |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Fri Apr 03, 2009 8:46 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| MQ_adi wrote: |
Hi,
Re-changes - I am sure that there were no code changes.
Thnx |
Check the QSTATUS of that particular queue when try to get that pdf from that queue.
DIS QSTATUS and look for IPPROCS count, it should not be '0'. Then your app is connected to that particular queue. Otherwise there is an issue with your in connecting.
Thanks. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Fri Apr 03, 2009 8:52 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
If you see the message in the queue then the getting application is in error.
Are you correctly setting or clearing the correlid and msgid?
My bet is it works once then starts 'failing' |
|
| Back to top |
|
|
| MQ_adi |
| Posted: Fri Apr 03, 2009 8:59 am Post subject: |
|
|
Novice
Joined: 03 Apr 2009
Posts: 13
|
Hi,
IPPROCS count is 0.
I have same queue manager for input and output queue. If my application is able to connect to input queue, what would be reason for connectivity problem with output queue?
Re-collelation id and ref id - we didn't change anything here.
thnx |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 03, 2009 9:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQ_adi wrote: |
| what would be reason for connectivity problem with output queue? |
2033 isn't a connectivity problem.
| MQ_adi wrote: |
| Re-collelation id and ref id - we didn't change anything here. |
The point is that maybe you should be.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| MQ_adi |
| Posted: Fri Apr 03, 2009 9:16 am Post subject: |
|
|
Novice
Joined: 03 Apr 2009
Posts: 13
|
Re-changing the code,
I have setup MQ and document in different enviroment and it's works there |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 03, 2009 9:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQ_adi wrote: |
Re-changing the code,
I have setup MQ and document in different enviroment and it's works there |
Twice in sucession?
This doesn't alter the fact that 2033 isn't a connection issue.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| MQ_adi |
| Posted: Fri Apr 03, 2009 9:25 am Post subject: |
|
|
Novice
Joined: 03 Apr 2009
Posts: 13
|
| I agree that it's not a connectivity problem. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Apr 03, 2009 9:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
A 2033 is not a configuration problem either, unless you've got some very bizarre configuration logic built into the consuming application.
Can we be a little more clear here? You're getting 2033's trying to read the OUTPUT from the document system, right?
Is this supposed to work according to a standard MQ request/reply, where the MsgId or CorrelId of the reply message is supposed to match the CorrelId or MsgId of the request message? Did the sending application change what options it specified? Did it change whether it's sending an Request or Datagram? |
|
| Back to top |
|
|
| MQ_adi |
| Posted: Fri Apr 03, 2009 9:43 am Post subject: |
|
|
Novice
Joined: 03 Apr 2009
Posts: 13
|
Sure, I will try to be clear.
There are basically 3 queue.
Q1 - This is the request queue where the application puts the xml.
Q2 - This is the response queue, application get the message id.
Q3 - This is the output queue, application gets the pdf from here.
While getting the pdf from the Q3, we are getting the 2033 error. Here are answers to your quries.
1. Yes, msg id
2. No
3. Datagram
Thnx |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Apr 03, 2009 9:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
No, that's not a standard request/reply paradigm.
It's still not clear how any MQ level configuration change could cause the message id's being placed on queue 2 to fail to match the msg ids of messages on queue 3.
But you really really really don't need queue 2 at all. Unless the document system's MQ interface is that weirdly written. |
|
| Back to top |
|
|
|
|
