| Author |
Message
|
| coolestcapri |
 Posted: Thu Mar 15, 2007 5:10 am Post subject: Issues with MQ command server on V6.0.1.1 |
 |
|
Newbie
Joined: 15 Mar 2007
Posts: 2
|
Hi
I am running MQ V6.0 on a Sun Solaris box. There are two queuemangers which are setup exactly the same way except that the CCSIDs are different. The problem is with one of the queuemanagers, the command server is hanging for that queuemanager and if we try to restart the command server it gives the following error
"AMQ8510: Command server queue is open, try again later".
I checked the queue manager logs and there is nothing except command server stopping and starting statements.
The other queuemanager is working perfectly fine. QPasa is installed on the server too.
Any ideas as to what the problem might be.
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Mar 15, 2007 7:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Check for messages on DLQ.
Is the command server "hanging" or continually restarting?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dhanaraj |
| Posted: Thu Mar 15, 2007 8:42 am Post subject: |
|
|
Voyager
Joined: 10 Aug 2004
Posts: 92
|
| check the status of the system.admin.command Queue and end the process that currently has the queue open for input. |
|
| Back to top |
|
|
| anantha sreenivasan |
| Posted: Wed Mar 21, 2007 1:55 pm Post subject: |
|
|
Acolyte
Joined: 26 Sep 2006
Posts: 72
|
You can perform the following steps:
a) Issue runmqsc display queue status command to trace the process that is holding the SYSTEM.ADMIN.COMMAND.QUEUE
display qs(SYSTEM.ADMIN.COMMAND.QUEUE) type(handle) all
b) End the process that currently has the queue open for input.
If the process no longer exists then try altering the queue by setting get or put disabled.
ALTER QL(SYSTEM.ADMIN.COMMAND.QUEUE) PUT(DISABLED)
This may clear up it in a few minutes. If altering the queue does not clear it up then you must recycle the qmgr. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Mar 21, 2007 7:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| anantha sreenivasan wrote: |
You can perform the following steps:
a) Issue runmqsc display queue status command to trace the process that is holding the SYSTEM.ADMIN.COMMAND.QUEUE
display qs(SYSTEM.ADMIN.COMMAND.QUEUE) type(handle) all
b) End the process that currently has the queue open for input.
If the process no longer exists then try altering the queue by setting get or put disabled.
ALTER QL(SYSTEM.ADMIN.COMMAND.QUEUE) PUT(DISABLED)
This may clear up it in a few minutes. If altering the queue does not clear it up then you must recycle the qmgr. |
As you're in V6 you can also use
dis conn(*) where (objname eq SYSTEM.ADMIN.COMMAND.QUEUE)
Then use the conn id # obtained to
stop conn(conid#)
This should also get rid of a stale connection...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| anantha sreenivasan |
| Posted: Thu Mar 22, 2007 9:46 am Post subject: |
|
|
Acolyte
Joined: 26 Sep 2006
Posts: 72
|
| How does a display of connection details differ from display of IPPROCS or OPPROCS of a Queue Status? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 22, 2007 9:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| anantha sreenivasan wrote: |
| How does a display of connection details differ from display of IPPROCS or OPPROCS of a Queue Status? |
How does a dog show differ from a cat show?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| coolestcapri |
| Posted: Mon Mar 26, 2007 6:55 am Post subject: |
|
|
Newbie
Joined: 15 Mar 2007
Posts: 2
|
jefflowrey : There are no messages stuck in the system dead letter queue.
The command server is not restarting but just hanging, when ti try to start it , it says its already running. When i restart the qmgr, eveything looks fine for about 2 mins, then the command server goes back to hanging again.
The persistence for the SYSTEM.ADMIN.COMMAND.QUEUE is set to no. Also I see a process on the queue, when i try to kill it , it says the process doesnt exist. We are using Qpasa on the server to monitor MQ. And looks like its one of the QPasa proceses. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 26, 2007 7:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| coolestcapri wrote: |
| We are using Qpasa on the server to monitor MQ. And looks like its one of the QPasa proceses. |
Time to give the vendors a quick nudge perhaps..... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Mar 26, 2007 10:05 am Post subject: Different CCSID's eh? |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
One thing I have found is that after creating a qmgr and then cganging the CCSID with an ALTER QMGR command, utilities such as MQExplorer can see the QMGR but can't open it until the QMGR has been stopped and restarted.
I'm just wondering if this is the problem here?
Just a thought, can you access the QMGR from a remote system using MQExplorer?
This issues PCF commands just like Qpasa etc does.
/Stephen D
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
