|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
amqmdain to end a QM - options? |
« View previous topic :: View next topic » |
Author |
Message
|
PeterPotkay |
Posted: Thu Oct 21, 2004 7:24 am Post subject: amqmdain to end a QM - options? |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Does a client app that connects and then does MQOPENs / MQGETs without the FAIL_IF_QUEISCING option prevent a QM from coming down if I use amqmdain?
amqmdain end MyQM
Is that the same as endmqm -i, or endmqm -c?
My QM would not end using this command, and we had to reboot the server. Windows 2000 MQ 5.3 CSD04
My logfile for the amqmdain end MyQM throws the error:
ERROR: could not get the task list
The error logs show this all night:
Code: |
----- amqrmrsa.c : 467 --------------------------------------------------------
10/21/2004 02:46:55
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'HIGIAOD1' failed with reason code
2161.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 425 --------------------------------------------------------
10/21/2004 02:46:55
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'CDS.CALLIGO' ended abnormally.
ACTION:
Look at previous error messages for channel program 'CDS.CALLIGO' in the error
files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
|
Using TransactionVision, I see today that the app connecting over this channel is issuing MQGETs without FAIL_IF_QUIESCING, as well as the occasional MQOPEN that is done, also without FAIL_IF_QUIESCING. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
JasonE |
Posted: Fri Oct 22, 2004 2:18 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
amqmdain end is the same as an immediate shutdown of the queue manager |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Oct 22, 2004 5:48 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Not that I don't trust ya, buuuuuuut, is this documented anywhere? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
JasonE |
Posted: Fri Oct 22, 2004 5:52 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
No
It was originally a controlled (normal) shutdown, but had to be changed to immediate because you cant stop an operating system shutdown indefinitely, and we need to stop the qmgrs during an os shutdown |
|
Back to top |
|
 |
PeterPotkay |
Posted: Thu Jan 20, 2005 3:17 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
So, IBM confirmed that amqmdain acts like a Controlled shutdown, and there is no way to make it act like endmqm -i. I opened up a request for adding this option, and got the following response:
>>amqmdain should support an immediate (not just controlled) shutdown of the QM
Accepted- IBM agrees with the request and a solution is desirable and feasible. IBM intends to provide a solution. However, IBM's plans may change, and no commitment is made that a solution will be provided.
But, I still wonder why my Client Concentrator takes sooooooooo long to end if I use amqmdain end. On the QM where there are few clients connected, it comes down in about a minute. On the QM that has a couple of hundred of clients connected, it takes 45 minutes !!! And all 3 error logs (at 1MEG each) are filled with errors saying the channels are ending, that QM is ending, etc.
I really would like to be able to bring this Windows QM down every night. What I don't understand is why does the QM take so long to end. Could it be the barrage of reconnect attempts? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
PeterPotkay |
Posted: Thu Jan 20, 2005 5:26 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Neil on the listserver suggested I use endmqm -i to end the QM, and then use amqmdain to start it up so it runs as a Service.
Using endmqm -i QM1, the QM, channel init and command server did come down, but the listener was left running. So I then issued endmqlsr -m QM1, and the listener ended.
amqmdain then was able to start the QM back up, and the channel init command server and the listener started up.
I have always been told never to mix the command line commands with amqmdain/MQServices, but this seems OK.
Until amqmdain supports -i, is this a safe way to do it? _________________ Peter Potkay
Keep Calm and MQ On |
|
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
|
|
|
|