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 » Queue monitor

Post new topic  Reply to topic Goto page Previous  1, 2
 Queue monitor « View previous topic :: View next topic » 
Author Message
jefflowrey
PostPosted: Fri Dec 17, 2004 6:05 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Nigelg wrote:
I still like my idea about the queue depth events though.


It's a reasonably good idea.

Assuming that he doesn't need to log records at not only 1000 and 2000, but 3000, 4000, 5000, 6000, ..., n000...
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
EddieA
PostPosted: Fri Dec 17, 2004 9:59 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Quote:
Assuming that he doesn't need to log records at not only 1000 and 2000, but 3000, 4000, 5000, 6000, ..., n000...

Why. You initially set Queue High at 1000. Disable Low. Then, when Queue High triggers, you set Queue High to 2000, Queue Low to 1000 and Enable both. Then, if Queue High trips again, you set High to 3000, Low to 2000. However, if Low trips, then set High to 1000, and disable Low. Repeat ad nauseum. Always assuming that the monitoring application can react fast enough. It may also have to check Queue Depth to make sure that that message 1000 that caused the "trip" hasn't already been read, along with 999, and 998, before resetting the values.

I know it's not the way Queue High/Low is meant to be used, but this was a strange request to start with.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Fri Dec 17, 2004 10:52 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7723

Do you think they really care that the queue went to 2000 at EXACTLY 12:45:01.4545445?

I am willing to bet that simply doing an MQINQ call every minute would suffice. If the depth is >1000, record the current time and the current depth. Easy enough to check for any multiple of 1000 with a CASE statement.


Unless I am missing something, this is turning out to be waaaaay to complicated.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » Queue monitor
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.