| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ performance checks |
« View previous topic :: View next topic » |
| Author |
Message
|
| mrfridaynight |
 Posted: Sun Jun 08, 2008 11:36 pm Post subject: MQ performance checks |
 |
|
Apprentice
Joined: 13 Nov 2006
Posts: 44
|
Hi Guys,
Where can i do basic MQ performance checks to see if my MQ environment is running optimally.
I notice on some of my Queue Managers and Queues, the messages remain for about 40 sec before being picked up for forworded along.
Thanks in advanance. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Mon Jun 09, 2008 12:24 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
better option is to buy some monitoring tools.
which helps you to get the alerts.
messages remaining in the queue should be various reasons
if target is not ready to pick up the messages.
Trigger
Channel etc etc.
You have to troubleshoot on this matter and find out it.
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mrfridaynight |
| Posted: Mon Jun 09, 2008 2:57 am Post subject: |
|
|
Apprentice
Joined: 13 Nov 2006
Posts: 44
|
I use Qpasa to montior our queues. I receive a lot of false alerts as when i do look at the queues, the messages are gone.
When constantly watching the queues, this is when i noticed the messages remain for 40 sec before moving on.
I just thought there are some parameters i can check to speed things up. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Mon Jun 09, 2008 10:10 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
When you say the messages are not "moving on", are you referring to messages in a transmit queue?
If the messages are not "moving on" from a local queue, the delay is most probably an issue with the application that is getting the messages.
You can avoid false alerts in QPasa several different ways, depending on what reflects a situation about which you are concerned. For example, you can put a delay in the alert itself, so that it only fires if the queue remains at a certain depth for a specified period. Or, you can alert if the queue reaches a specified depth and the IPPROCS are a specified value. Or you can alert on IPPROCS only, if you always expect there to be handles into the queue.
These are just examples; you can do about anything with complex QP alerts. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jun 09, 2008 11:19 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| the messages remain for about 40 sec before being picked up |
Are you saying that all messages sit in the queue for 40 seconds before the getting application comes to life and gets the first message? Or are you saying that it takes 40 seconds to consume the last message in the queue?
If there are millions of messages, it might take the getting application a while to process all of them.
What are the differences between the MQs that you believe to be slow and the MQs that appear to be faster? What hardware platfforms? What speed processor(s)?
WMQ v6 has some queue attributes that will tell you about the oldest message in the queue, and how long it's been there.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
