| Author |
Message
|
| shahs |
 Posted: Fri Aug 22, 2008 8:10 am Post subject: Messages piling up on SYSTEM.CLUSTER.COMMAND.QUEUE |
 |
|
Novice
Joined: 28 Mar 2008
Posts: 15
|
Hi,
We have MQ v 6.0.2.3 installed on a Solaris machine and I see messages piling up on the SYSTEM.CLUSTER.COMMAND.QUEUE on this queue manager which is a full repository.
I am also not able to see the Cluster queues from this repository .
Plz suggest what can be done. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Aug 22, 2008 12:30 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Moving to Cluster Forum.
Sounds like your Repository Manager is fried. Does anything have the queue open for gets? You cannot stop or start that component yourself. Only a QM restart will restart it.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| choupw |
| Posted: Sun Jun 19, 2011 12:26 am Post subject: |
|
|
Newbie
Joined: 19 Jun 2011
Posts: 1
|
if the amqrrmfa process not exist,get it like this :
/usr/mqm/bin/amqrrmfa -m BROKER2_QM(your qmgr name) -t2332800 -s2592000 -p2592000 -g5184000 -c3600 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jun 19, 2011 4:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| choupw wrote: |
if the amqrrmfa process not exist,get it like this :
/usr/mqm/bin/amqrrmfa -m BROKER2_QM(your qmgr name) -t2332800 -s2592000 -p2592000 -g5184000 -c3600 |
Totally unsupported and inadequate. The right thing to do if the process does not exist is to bounce the qmgr. If that does not fix the problem, open a PMR.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Sun Jun 19, 2011 7:29 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
| choupw wrote: |
if the amqrrmfa process not exist,get it like this :
/usr/mqm/bin/amqrrmfa -m BROKER2_QM(your qmgr name) -t2332800 -s2592000 -p2592000 -g5184000 -c3600 |
Totally unsupported and inadequate. The right thing to do if the process does not exist is to bounce the qmgr. If that does not fix the problem, open a PMR.
|
Depending on what's wrong even that may not fix it. I've seen the process fail when an explicit CLUSSDR has been defined from a Full Repository to a Partial Repository, and the first message on the repository queue is generally a 'poison' message.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| skoobee |
| Posted: Sun Jun 19, 2011 10:09 pm Post subject: |
|
|
Acolyte
Joined: 26 Nov 2010
Posts: 52
|
| If the repos mgr has ended, which can be determined by a simple ps list for the qmgr, there will be at least one FDC, with probe ZX005025 (or ZX005030, I forget which) from the EC, saying that the repos mgr is not running. There may well also be an FDC from the repos mgr itself, with some sort of reason why it ended, and a msg in the error logs saying that it has ended and will restart in 600 seconds. |
|
| Back to top |
|
|
|
|
