|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Unable to get message from Queue |
« View previous topic :: View next topic » |
Author |
Message
|
ajaykumar |
Posted: Mon Sep 22, 2008 12:54 am Post subject: Unable to get message from Queue |
|
|
Novice
Joined: 20 Sep 2008 Posts: 10
|
Hi ,
In our project we are using Websphere MQAPI to connect to queue manager ,put message, get message, to check for message availablity and also to disable trigger. We came across a scenario where the current depth was >0(i.e Message is present in the queue) but we were getting 2033 when we tried to get the message. We initially thought they might be a uncommitted messages but we found that they are all committed. We tried to nail down to the reason and were able to find a reason it was actually that we have an inbuilt logic in the code that segments the message if it is beyond a specified length and for the last segment we used to set the flag as 'Last Segment' and even when the message doesnt need to be segmented we were setting the 'Last Segment' Flag to it. But even with this we were able to get messages from the queue in UNIX and Windows but we faced the issue in LINUX environment, and so we thoought that may be setting the 'Last Segment' flag for every message even though segmentation is not required caused this issue. So we thought to set the 'Last Segment' flag only to the Last segment of those messages which we were segmenting and not to every message and it worked fine in LINUX . Please tell if similar issue has been faced by anyone or confirm that why this would have happened.
With Best Regards,
Ajay. |
|
Back to top |
|
 |
gbaddeley |
Posted: Mon Sep 22, 2008 7:30 pm Post subject: Re: Unable to get message from Queue |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
ajaykumar wrote: |
Hi ,
In our project we are using Websphere MQAPI to connect to queue manager ,put message, get message, to check for message availablity and also to disable trigger. We came across a scenario where the current depth was >0(i.e Message is present in the queue) but we were getting 2033 when we tried to get the message. |
Ajay, you should not be checking the current depth to decide if you should attempt to get a message from it.
Just go ahead and try to get a message. If there is nothing to get it will just return a 2033 reason code. _________________ Glenn |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Sep 22, 2008 7:36 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
I think Glenn missed the point here:
ajaykumar wrote: |
so we thought that may be setting the 'Last Segment' flag for every message even though segmentation is not required caused this issue. So we thought to set the 'Last Segment' flag only to the Last segment of those messages which we were segmenting and not to every message and it worked fine in LINUX |
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
gbaddeley |
Posted: Tue Sep 23, 2008 7:53 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
fjb_saper wrote: |
I think Glenn missed the point here |
Sorry, I re-read the post, and I did miss the point. _________________ Glenn |
|
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
|
|
|
|