| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Slow endmqm and SVRCONN channel errors |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Fri Oct 24, 2003 4:44 am Post subject: Slow endmqm and SVRCONN channel errors |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
When I tried to do an immediate stop (thru the MQServices GUI) of this QM, it took about 10 minutes before it finally came down. The Initiator and the Listner came down almost immediatly, but the QM and Command Server took the full 10 minutes. The error log for the QM had the follwong:
*******************************************************************************************************
---- amqccita.c : 2781 -------------------------------------------------------
10/23/2003 21:07:20
AMQ9411: Repository manager ended normally.
EXPLANATION:
The repository manager ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
10/23/2003 21:07:21
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
********************************************************************************************************************
Followed by about 700 of the below message repeated over and over:
************************************************************************************************************
----- amqrmsaa.c : 425 --------------------------------------------------------
10/23/2003 21:07:22
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'HIGIDGD1' failed with reason code
2162.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 425 --------------------------------------------------------
10/23/2003 21:07:22
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'HIGIDGD1' failed with reason code
2162.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 425 --------------------------------------------------------
*****************************************************************************************************************
followed by about 700 instances of the following error:
*******************************************************************************************************************
----- amqrmrsa.c : 467 --------------------------------------------------------
10/23/2003 21:07:59
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'HIGIDGD1.CLIENT' ended abnormally.
ACTION:
Look at previous error messages for channel program 'HIGIDGD1.CLIENT' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
10/23/2003 21:07:59
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'HIGIDGD1.CLIENT' ended abnormally.
ACTION:
Look at previous error messages for channel program 'HIGIDGD1.CLIENT' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
***************************************************************************************************************
What would this indicate? I am guessing there is maybe some client app(s) out there trying to connect to this QM over this channel (HIGIDGD1.CLIENT is a SVRCONN) over and over so fast the QM can't catch a break to end?
It finally did end and came back up cleanly.
*******************************************************************************
10/23/2003 21:12:20
AMQ8004: WebSphere MQ queue manager 'HIGIDGD1' ended.
EXPLANATION:
WebSphere MQ queue manager 'HIGIDGD1' ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/23/2003 21:15:47
AMQ8003: WebSphere MQ queue manager 'HIGIDGD1' started.
EXPLANATION:
WebSphere MQ queue manager 'HIGIDGD1' started.
ACTION:
None.
-------------------------------------------------------------------------------
10/23/2003 21:15:48
AMQ9410: Repository manager started
EXPLANATION:
The repository manager started successfully.
ACTION:
None.
------------------------
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| AlainB |
| Posted: Fri Oct 24, 2003 5:00 am Post subject: |
|
|
Voyager
Joined: 31 Oct 2002
Posts: 79
Location: Belgium
|
We had such a kind of problem on a queue manager where lots of client application were connecting in client mode. Once it took 1/4h before completely ending.
In urgency case, a 'dirty' solution is to kill the program driving the connexion (can't remember its name).
_________________
Alain Buret
Visit http://www.fosdem.org |
|
| Back to top |
|
|
| mqonnet |
| Posted: Fri Oct 24, 2003 8:03 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Peter, i think you got the idea right. And i believe you got this erorr because some client was trying to establish a connection while your qm was going down.
But what struck me from your explaination was that your Listener went down. I think if the listener is completely down, then there is no way a client can communicate with the qm on a server(MQ). So, i would think that the listener either did not come down cleanly or was still doing some stuff. I have occassionaly seen wrong info in MQ Explorer/Services GUI. Hence i always try to use command prompt instead.
What i would suggest you for the next occurance is to manually kill the listener and see if it makes any difference. Also make sure you have ended all the listeners for this qm.
Cheers
Kumar |
|
| 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
|
|
|
|
