| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| triggering question |
« View previous topic :: View next topic » |
| Author |
Message
|
| crossland |
 Posted: Fri Apr 30, 2004 3:50 am Post subject: triggering question |
 |
|
Master
Joined: 26 Jun 2001
Posts: 248
|
An application puts 24 messages onto a queue which is set to trigger first - the messages are all put within a unit of work.
The application then issues a rollback and the depth goes back to 0. Triggering does not happen until this point.
The triggered application is then failing as there are no messages on the queue.
Can anyone explain why triggering is occuring in this case?
Thanks,
Tim |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Apr 30, 2004 4:43 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Its working as designed.
See Chapter 14 of the Application Programming Guide.
Lets say you put all 24 messages to the queue under syncpoint, and the trigger message is generated, but not committed. That trigger message is committed when the putting app commits, and your app will be started at that time. But what happens if message #25 lands from a different UOW after the first 24 are put but not yet committed? If the first 24 are backed out, and MQ also backed out the trigger message, then message 25 would be stranded with no trigger message, since the queue went from 25 to 1, not 0 to 1.
All triggered apps should read the queue until 2033. All triggered apps should handle getting a 2033 on their first MQGET with no problems.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
