Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
I'd guess that you hit one of two things.
You had messages on the queue that were expired. This would allow the curdepth to display the 5. When you ran amqsbcg, MQ realized the messages were expired and threw them away. This causes your next curdepth to display the 0.
You had uncommitted messages on the queue. You attempt to browse them and can't see them because they aren't available. An application then rolled back the messages. You issued your curdepth and got the 0.
Posted: Mon Apr 21, 2003 9:29 am Post subject: commit point issue.
Centurion
Joined: 28 Jan 2003 Posts: 109 Location: Colorado
Additionally the messages may not be committed yet. Uncommited units of work still register when looking at curdepth... For example messges can be placed on a queue and appear but untill the putting app has commited them they are not available to be consumed.... On the other hand a getting application could have read the messages off the queue and not commited the destructive read... In this case the messaes are there but not available to be consumed by another application.
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