|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Losing Messages after killing a unix application |
« View previous topic :: View next topic » |
Author |
Message
|
russell |
Posted: Thu Oct 04, 2001 11:33 pm Post subject: |
|
|
 Newbie
Joined: 24 Jun 2001 Posts: 8
|
Hi all
We have a unix application which is a MQ Client reading from a queue with a -1 on the wait time (ie it waits forever).
If I kill this application, then I put a message on the queue it disappears.
I have tried this with the recieving application restarted, and still the same effect.
Does anyone know whats happening and is there a solution?
regards Russell |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Oct 05, 2001 11:44 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
If the unlimited Get wait is done without the syncpoint option, you will see the first message put to the queue after you abend the app dissappear. The surrogate does not realize there is no app on the other side of the client connect, so it sends the message off. To do this, it needs to remove it from the queue. Since you don't have the syncpoint option set, it can't roll it back once it finds out that there is no app on the other side.
This is the exact reason why getting applications with a client connect must almost always use syncpoint on their gets. It insures the message will be replaced in this scenario.
_________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
russell |
Posted: Sun Oct 07, 2001 4:33 pm Post subject: |
|
|
 Newbie
Joined: 24 Jun 2001 Posts: 8
|
Thanks
I sort of thought that was the problem, The odd missed message after a crash isnt vital in my app, so it just a decision to add the overhead of syncpoint.
regards
Russell |
|
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
|
|
|
|