| Author |
Message
|
| mqsi |
 Posted: Thu May 05, 2005 1:09 am Post subject: Command server is not coming up in solaris |
 |
|
Apprentice
Joined: 11 Jun 2004
Posts: 33
|
Started the command server using strmqcsv TEST_QMGR. (MQ5.3 on Solaris)
SYSTEM.ADMIN.COMMAND.QUEUE has 7 messages. Is this the reason that the cmdsvr is not coming up. Could't clear the messages as queue has open handles on it.
can someone suggest how tofix the issue.
Regards |
|
| Back to top |
|
 |
| oz1ccg |
| Posted: Thu May 05, 2005 2:53 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
what is in the /var/mqm/errors/AMQxxx.LOG ?
and /var/mqm/qmgrs/<qmgr>/errors/AMQxxx.LOG ?
(I hope the paht is ok)
There are the log-files, and there should be a clue.
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu May 05, 2005 5:46 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Messages on the queue won't keep the command server from coming up. As oz1ccg suggested, you need to look elsewhere. Does the command itself throw an error and are there any *.FDC files in the error directories? |
|
| Back to top |
|
|
| JT |
| Posted: Thu May 05, 2005 6:30 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
What id are you using to issue the strmqcsv command? Is it in the mqm group?
Check the processes running on the server, is 'AMQPCSEA TEST_QMGR' running?
Issue the command: DIS QS(SYSTEM.ADMIN.COMMAND.QUEUE) TYPE(HANDLE) ALL
Does the AMQPCSEA process (APPLTAG) have the queue open for input? |
|
| Back to top |
|
|
| mqsi |
| Posted: Thu May 05, 2005 10:37 pm Post subject: |
|
|
Apprentice
Joined: 11 Jun 2004
Posts: 33
|
queue is open in EXCLUSIVE mode:
here are the details..
QUEUE(SYSTEM.ADMIN.COMMAND.QUEUE) PID(1598)
APPLTAG(amqpcsea) TID(1)
APPLTYPE(SYSTEM) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(EXCL) INQUIRE(YES)
OUTPUT(NO) SET(NO)
when i issue the strmqcsv command, this is the error i'm getting.
AMQ8510: Command server queue is open, try again later.
no log files are updated and no .FDC files are created.. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 06, 2005 3:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So it's telling you that the command server is already running.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqsi |
| Posted: Fri May 06, 2005 3:26 am Post subject: |
|
|
Apprentice
Joined: 11 Jun 2004
Posts: 33
|
when i do a dspmqcsv on the queue manager
WebSphere MQ command server status . . : Stopped[b]
qmstatus.ini shows CmdSvrStatus=EndedUnexpectedly
couldn't browse the queues in PQEdit with cmdsvr not running exception
but runmqsc is working on the queue manager.
looks little tricky atleast for me
[/b] |
|
| Back to top |
|
|
| clindsey |
| Posted: Fri May 06, 2005 5:03 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Try disabling the queue for gets. That may stop the process.
alter ql(SYSTEM.ADMIN.COMMAND.QUEUE) get(disabled).
If that doesn't stop it, you may have to kill amqpcsea, or bounce the queue manager if you can.
Then set the queue back to get enabled.
Personally, I would clear the messages off the queue before starting the command server again. It has been a while and several maintenance releases ago, but I have been able to shut down a command server by sending a poorly formed PCF messages.
Charlie |
|
| Back to top |
|
|
|
|
