| Author |
Message
|
| PeterPotkay |
 Posted: Fri Mar 20, 2009 12:34 pm Post subject: SYSTEM.JMS.PS.STATUS.QUEUE backing up |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Windows 2003
MQ 6.0.2.5
Single app using MQ's built in Pub/Sub Broker. A few publishers, a few subscribers.
The SYSTEM.JMS.PS.STATUS.QUEUE gets a new messge into it every few minutes. The messages are persistent with unlimited Expiry, so they are piling up. They go back months. Luckily they are small; all contain only this string in the payload:
MQJMS_PS_JVM_STATUS_MSGbackout
Each has an MQMD Backout count of 1, except for the 1st message on the queue whose backout count is >25.
Same problem in DEV, QA and PROD.
What is supposed to consume these messages?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Mar 21, 2009 9:10 am Post subject: Re: SYSTEM.JMS.PS.STATUS.QUEUE backing up |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
Same problem in DEV, QA and PROD.
What is supposed to consume these messages? |
I thought that was specified in the pub/sub manual.
Can't remember off hand and can't be bother to look it up right now...
Check as well the rmm part...
Are you sure you are providing a reply to Destination when subscribing? Are you having the subscriber check the messages there to know if the subscription was successful? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Mar 21, 2009 10:38 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Mar 21, 2009 10:45 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I tried that Cleanup utility on the DEV server. It had no impact on the messages on the SYSTEM.JMS.PS.STATUS.QUEUE.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 21, 2009 5:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Mar 23, 2009 10:39 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
FORCE requires all Pub/Sub apps to be disconnected. I am working with the app to try this in DEV.
You think it makes a difference regular versus client?
But even if this fixes it and cleans up all the messages, it only solves the symptom, and not the root cause - which is why are these messages not being consumed on a regular basis.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Mar 23, 2009 8:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
FORCE requires all Pub/Sub apps to be disconnected. I am working with the app to try this in DEV.
You think it makes a difference regular versus client?
But even if this fixes it and cleans up all the messages, it only solves the symptom, and not the root cause - which is why are these messages not being consumed on a regular basis. |
As my last 2 links indicated the cleanup is an admin task that can be delegated to a program. This queue holds some kind of pointer to defunct subscriptions and some kind of such, and allows the qmgr to get rid of those that is if I understood the brief overview I read... it looks like you are supposed to run some sweeper program against the Pub/sub qmgr and that would take care of your queue....
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Apr 21, 2009 2:35 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
IBM had me set the SUBSTORE property in the QCFs to the value BROKER. It was MIGRATE. Once this was set to BROKER these messages were no longer produced. Then I manually deleted all the old messages from the SYSTEM.JMS.PS.STATUS.QUEUE.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
