| Author |
Message
|
| ae06425 |
 Posted: Wed May 20, 2009 1:38 pm Post subject: messages disappear by any MQGET call (browse, get etc..) |
 |
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
Client is putting 100 messages on MQ queue
All Messages are disappearing when any MQGET call(get, browse etc..) issued against the queue...
Checking queue manager deadletter queue, not there either....
Can smo tell me what would be wrong with message?
where the messages would be goint to?
any way to see message header info without loosing msg since any mqget call makes the msg disappear?
msg expiry set to -1 (by app)
messages are persistent (set by application).
mq server version 5.3 CSD10
Client's other apps are working fine....
Pls let me know |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed May 20, 2009 1:52 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Sure they're actually set to non-expire? The 'symptoms' you have described certainly sound as though they're being expired. Try using the amqsbcg sample immediately the messages are put, and pipe the output to a file so you can inspect the MQMD.
I never believe what developers tell me - until they prove it empirically 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| ae06425 |
| Posted: Wed May 20, 2009 2:02 pm Post subject: |
|
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
MQ client put 100 msg and I see them in the queue
with "dis ql(queue_name) curdepth".
messages are discarded with any GET or BROWSE call to the queue including "amqsbcg". Hence, I cannot use amqsbcg to see header info.
other than message expiry what can cause this?
we make sure msg expiry set to -1.
thanks |
|
| Back to top |
|
|
| exerk |
| Posted: Wed May 20, 2009 2:06 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Can you step through the code? Still sounds to me that they're set to expire. You may be over-riding the set value somewhere in the code.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| ae06425 |
| Posted: Wed May 20, 2009 2:20 pm Post subject: |
|
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
Just talked to the app person...
They are publishing msg through some java application server or java client factory etc... Not a websphere app server though.
So I think we need to check what the settings over there that may be change msg expiry or some other setting that might be causing this.
if need to check java factory what should we be looking for?
Thanks |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed May 20, 2009 7:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
There's a lot of things that can influence this.
Depending on the JNDI settings the queue settings may have priority or the app settings may have priority etc... Sometimes the broker settings may change that. You need to check the message from the moment it is put to the moment it hits the destination queue.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ae06425 |
| Posted: Thu May 21, 2009 5:37 am Post subject: |
|
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
Can I have more details as to what to look for spesifically in JNDI settings?
What JNDI parameters' settings make more sense to check
thanks |
|
| Back to top |
|
|
| zpat |
| Posted: Thu May 21, 2009 5:48 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
If the expiry is set in the app - (most programs don't bother and get the default of non-expiring) then it is almost certainly getting this wrong.
-1 can mean different things in some languages and variable types - try NOT setting the expiry value (or set to a large positive number) and see what happens. |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Thu May 21, 2009 5:52 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
| Quote: |
| All Messages are disappearing when any MQGET call(get, browse etc..) issued against the queue. |
Have you check that for how long messages remain in queue after disable the GET in queue?
Situation 1:
A. if it remains in the queue for longtime it ensure that there is no problem in message expiry time.
B. Now bringdown the client application and enable get call and browse the message from the queue in a file.
If situation 1[A] fails then the expiry time is not set correctly.
If situation 1[B] fails then please send the queue status.
Best Regards,
Aditya
Best Regards.
Aditya
[/quote] |
|
| Back to top |
|
|
| ae06425 |
| Posted: Thu May 21, 2009 7:25 am Post subject: |
|
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
Thanks everyone for looking and giving your responses.
Issue resolved.
App person changed the JMS template they were using.
With the new template it is working fine.
I am able to browse and app is able to retrieve msg from queue without msg being discarded.
We are digging more into what is the difference between the old and the new templates being used, their settings etc..
thanks again |
|
| Back to top |
|
|
|
|
