ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » CURDEPTH problem?

Post new topic  Reply to topic
 CURDEPTH problem? « View previous topic :: View next topic » 
Author Message
GregJ
PostPosted: Thu Apr 17, 2003 10:38 am    Post subject: CURDEPTH problem? Reply with quote

Acolyte

Joined: 24 Oct 2001
Posts: 69
Location: Markham, On. Canada

On a unix Queue manager i have a local queue called 'qlocal1' If i do a dis ql(*) curdepth, my queue shows a depth of 5.

Now i do an amqsbcg and all i get is 'no more messages'

When i go back to dis ql(*) curdepth it is now (0)

What up with that?
G
Back to top
View user's profile Send private message
bower5932
PostPosted: Thu Apr 17, 2003 10:46 am    Post subject: Reply with quote

Jedi Knight

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.

I'd guess that the messages were expired.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
tillywern
PostPosted: Mon Apr 21, 2003 9:29 am    Post subject: commit point issue. Reply with quote

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.


hope this helps things be more clear.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » CURDEPTH problem?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.