| Author |
Message
|
| czaszek |
 Posted: Wed Sep 02, 2009 1:24 am Post subject: how to check number of consumers on MQ level |
 |
|
Apprentice
Joined: 30 May 2006
Posts: 36
Location: Poland
|
Hi
System which is connected to our MQ queue manager (via SVRCONN channel) complains that the messages are in a queue in an incorrect order.
We are are amost sure that it is not true because our PUTting system logs every message during processing and it shows that messages were put in correct order.
Is there any way to check (e.g. queue status) how many consumers are actively in parallel consuming messages from a queue?
(maybe some traces, but human readible)
Thanks in advance for help
Lukasz |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Wed Sep 02, 2009 1:33 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
Check the open input count (IPROCS) on a queue. This shows how many apps have the queue open for read but you have to bear in mind that they may not necesserily actually be consuming a message at that point in time - You should check your application logs for that.
You could do an MQ trace which will show messages being read off but this may be a little too low level. |
|
| Back to top |
|
|
| czaszek |
| Posted: Wed Sep 02, 2009 3:02 am Post subject: |
|
|
Apprentice
Joined: 30 May 2006
Posts: 36
Location: Poland
|
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed Sep 02, 2009 3:46 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
| Or enable queue monitoring (only need to do it on the individual queue) and view the queue status... you get more details that way. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Wed Sep 02, 2009 5:47 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
DISPLAY QSTATUS(queue in question) TYPE(HANDLE) ALL will provide the PID of the reading app and you can grep to see who is that.
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 02, 2009 5:47 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| System which is connected to our MQ queue manager (via SVRCONN channel) complains that the messages are in a queue in an incorrect order. |
By system, you mean the consuming application, yes? So, your messages have affinity for other (previous) messages.
Is this a new application?
_________________
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 |
|
|
| fjb_saper |
| Posted: Wed Sep 02, 2009 5:54 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Check the queue's setup. The default delivery sequence is priority (and FIFO within the priority) . You may set the queue's delivery sequence to FIFO.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 02, 2009 10:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You should also search for previous discussions on message order. Just because messages are put in a given order, it's not certain they'll be presented to the receiving application in that order. It's certainly not guaranteed by the queue manager.
Another reason why message affinity is a bad idea.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Sep 02, 2009 4:09 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Vitor wrote: |
You should also search for previous discussions on message order. Just because messages are put in a given order, it's not certain they'll be presented to the receiving application in that order. It's certainly not guaranteed by the queue manager.
Another reason why message affinity is a bad idea. |
Correct, MQ does not guarantee message order.
If the consuming app requires an affinity for message order, an order identifier should be stored in CorrelId or the message data. The consuming app then needs to marshall the messages into the correct order using temporary storage, such as a database table.
_________________
Glenn |
|
| Back to top |
|
|
|
|
