| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Broker System queue full..possible reasons? |
« View previous topic :: View next topic » |
| Author |
Message
|
| veeruk |
 Posted: Sun Apr 02, 2006 1:59 pm Post subject: MQ Broker System queue full..possible reasons? |
 |
|
Acolyte
Joined: 13 Mar 2006
Posts: 73
|
Hi guys,
One of our production boxes has MQ Broker configured on it. Recently the SYSTEM.BROKER.DEFAULT.STREAM queue reached it's maximum depth (10000 messages). The surprising thing is problem is recurring every thursday around 3PM from the last 2 weeks.
Please suggest the probable reasons why is this happening.Also let me know of any solutions with which I can get rid of this problem.
Thank you,
Veeru. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sun Apr 02, 2006 2:07 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'd guess you have a subscriber that isn't picking up messages - or you have an application that is publishing more messages than your subscribers can handle.
And whenever there is an event that is recurring on a timed basis, then it is an application somewhere - and not MQ - that is at fault.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| veeruk |
| Posted: Sun Apr 02, 2006 2:17 pm Post subject: |
|
|
Acolyte
Joined: 13 Mar 2006
Posts: 73
|
But for this not to happen in the future, atleast we should be ready to handle the situation. So can I suggest the following options to my team?
a) Increase the maximum queue depth from the current 10000 messages to 50000 so as to handle the input messages, which shouldn't cause any interruption to the production box.
b) Find out the scheduled job which is putting the messages at that specific time and reschedule the job so that the broker and queue can handle the input messages.
c) Last option is to create another broker (child broker) under the existing broker(parent broker) so as to balance the work load.
Kindly let me know if I'm wrong at some point. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Apr 02, 2006 3:06 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
First you should make sure that the volume is correct, and see if you can tune the applications some so that the queue doesn't build up so high.
For instance, if for some reason the app builders have decided to create a durable subscriber and have the subscriber triggered - then maybe you should start the subscriber on a scheduled basis instead - to eliminate startup time delays after the publisher starts.
Or you can see about adding instances or threads to the subscriber so it can fetch and process messages faster.
Then look at increasing the maxdepth and adding another broker. But adding another broker will only help if the subscriber app can't start more than one instance or thread on the same queue - but that's not likely since it's using the Default stream. If it were opening the default stream queue for exclusive access - then every other subscriber using the default stream would throw errors.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
