| Author |
Message
|
| dude1 |
 Posted: Fri Sep 14, 2007 9:07 am Post subject: Q manager is quiescing automatically |
 |
|
Novice
Joined: 20 Feb 2007
Posts: 10
|
Hello all -
I am running a Websphere MQ V6.0 on a Windows Box...
I am not a MQ Expert... i just use some of its CPP API and communicate between app using MQ.....
recently i have been researching on a error that keeps showing up in the Q manager log pretty frequently.
The Q manager is quiescing automatically. I have no clue Y that is happening... there are some logs above and below the quiescing log ... but I have no clue Y would those logs show up either...
It will be great if some one can shred some light on me in this issue .... I am like searching a house in an unknown Island..
Thanks in advance for your help...
Badri
Here is the log (These set of logs just keeps repeating again and again )
----- amqccita.c : 3227 -------------------------------------------------------
9/12/2007 15:27:17 - Process(1768.1) User(mqserver) Program(amqrrmfa.exe)
AMQ9411: Repository manager ended normally.
EXPLANATION:
The repository manager ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
9/12/2007 15:27:17 - Process(2520.19738) User(mqserver) Program(amqrmppa.exe)
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrmssa.c : 2378 -------------------------------------------------------
9/12/2007 15:27:17 - Process(2520.19739) User(mqserver) Program(amqrmppa.exe)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'TESTQM1' failed with reason
code 2162.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 442 --------------------------------------------------------
9/12/2007 15:27:18 - Process(2056.1) User(mqserver) Program(runmqchi.exe)
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrimna.c : 941 --------------------------------------------------------
9/12/2007 15:27:18 - Process(1840.1) User(mqserver) Program(amqzmgr0.exe)
AMQ5025: The Command Server has ended. ProcessId(2072).
EXPLANATION:
The Command Server process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/12/2007 15:27:18 - Process(2520.19739) User(mqserver) Program(amqrmppa.exe)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TESTQM1_CH' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TESTQM1_CH' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 468 --------------------------------------------------------
9/12/2007 15:27:18 - Process(1840.1) User(mqserver) Program(amqzmgr0.exe)
AMQ5023: The Channel Initiator has ended. ProcessId(2056).
EXPLANATION:
The Channel Initiator process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/12/2007 15:27:18 - Process(1692.1) User(mqserver) Program(amqzmuc0.exe)
AMQ5041: The Queue Manager task 'ASYNCQ' has ended.
EXPLANATION:
The Queue Manager task ASYNCQ has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/12/2007 15:27:18 - Process(2088.3) User(mqserver) Program(runmqlsr.exe)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'TESTQM1' failed with reason
code 2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 442 --------------------------------------------------------
9/12/2007 15:27:18 - Process(2088.4) User(mqserver) Program(runmqlsr.exe)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'TESTQM1' failed with reason
code 2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 442 --------------------------------------------------------
9/12/2007 15:27:18 - Process(2088.3) User(mqserver) Program(runmqlsr.exe)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TESTQM1_CH' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TESTQM1_CH' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 468 --------------------------------------------------------
9/12/2007 15:27:18 - Process(2088.4) User(mqserver) Program(runmqlsr.exe)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TESTQM1_CH' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TESTQM1_CH' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 468 --------------------------------------------------------
9/12/2007 15:27:18 - Process(896.1) User(mqserver) Program(amqzmur0.exe)
AMQ5041: The Queue Manager task 'ERROR-LOG' has ended.
EXPLANATION:
The Queue Manager task ERROR-LOG has ended.
ACTION:
None.
-------------------------------------------------------------------------------
9/12/2007 15:27:18 - Process(2088.5) User(mqserver) Program(runmqlsr.exe)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'TESTQM1' failed with reason
code 2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 442 --------------------------------------------------------
9/12/2007 15:27:18 - Process(2088.5) User(mqserver) Program(runmqlsr.exe)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TESTQM1_CH' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TESTQM1_CH' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 468 --------------------------------------------------------
9/12/2007 15:27:19 - Process(1840.1) User(mqserver) Program(amqzmgr0.exe)
AMQ5027: The Listener 'LISTENER.TCP' has ended. ProcessId(2088).
EXPLANATION:
The Listener process has ended.
ACTION:
None. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Sep 14, 2007 10:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
A couple of possibilities off the cuff:
- the MQ Admins are closing it for reasons they feel are valid at times that work for them
- the queue manager is running under a personal user id and is closing when it's logged off.
Your first port of call - your MQ admins.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| UglyAngelX |
| Posted: Fri Sep 14, 2007 10:54 am Post subject: |
|
|
Voyager
Joined: 04 Dec 2001
Posts: 90
Location: BEARS FAN IN STEELER COUNTRY
|
| How often is this happening? Could it be a regularly scheduled reboot? This would show the QMGR ending and starting in the logs. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Fri Sep 14, 2007 11:38 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
A client had a similar thing happening on Solaris with WMQ v5.3 (I don't remember the CSD). They swore that there was no scheduled shutdown. Plus it happened very randomly between 4 to 6 weeks.
Anyway, they opened PMR with IBM and IBM said to go to the latest CSD and (I think it was either CSD12 or CSD13). IBM said when it happens again to send all error logs to IBM.
Guess what, in the last 8 months it has never happened again. Now they are upgrading to WMQ v6. 
I would suggest that you apply the latest FP.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| sidharth_bora |
| Posted: Sun Sep 16, 2007 8:31 pm Post subject: |
|
|
Voyager
Joined: 24 Nov 2005
Posts: 87
|
what does the FDC say ...
Sid |
|
| Back to top |
|
|
| dude1 |
| Posted: Mon Sep 17, 2007 7:59 am Post subject: |
|
|
Novice
Joined: 20 Feb 2007
Posts: 10
|
- the MQ Admins are closing it for reasons they feel are valid at times that work for them
NOPE the MQ admins does not touch the Q's....
- the queue manager is running under a personal user id and is closing when it's logged off.
I dont know what you mean by Q manager is running under personal User ID... but I know for sure... the Q manager is running even when the system is in the Control Alt Delete mode...(the login screen).. Also the settings in the Q manager is set to run even if the user is logged off...
--------------------------------------------------------------------
This happens very frequently.... some time repeats within the same day... some time.....3 to 4 times in a week...
----------------------------------------------------------------------
I guess if i couldnt find a possible solution ...opening a ticket with IBM would be the next step...
-----------------------------------------------------------------------
What is FDC?? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Sep 17, 2007 8:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guarantee your MQ Admins do touch the queues, and do start and stop the queue manager.
They may not be responsible for these particular occurrences.
But I'm confused that it is you that is trying to solve this problem, and not the MQ Admins. They should be dealing with any issues that come up with the queue manager, particularly if it is stopping randomly.
An FDC is specific kind of error file - so called because it ends with ".fdc".
You should be talking to your MQ Admins, and working heavily with them to troubleshoot this.
You should be troubleshooting this one step at a time. What is the first error that shows up after a restart? What other things are going on at the time that error occurs?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| tleichen |
| Posted: Mon Sep 17, 2007 11:18 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
| dude1 wrote: |
| ...NOPE the MQ admins does not touch the Q's.... |
Really?
| dude1 wrote: |
| ...I dont know what you mean by Q manager is running under personal User ID... but I know for sure... the Q manager is running even when the system is in the Control Alt Delete mode...(the login screen).. Also the settings in the Q manager is set to run even if the user is logged off... |
I think you're confusing your userid with that of the q manager. "Control Alt Delete mode"? Hmmm.... that's one I hadn't heard... 
| dude1 wrote: |
| ...What is FDC?? |
 (sigh)
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
|
|
