| Author |
Message
|
| Praveensc |
 Posted: Mon Oct 18, 2010 11:19 pm Post subject: Unable to start the queue manager |
 |
|
Novice
Joined: 27 Feb 2008
Posts: 23
|
Hi,
I just created the qmgr CLUSQM2 on my local machine and try to start it with strmqm CLUSQM2 commadn. getting the error as
WebSphere MQ queue manager 'CLUSQM2' starting.
13 log records accessed on queue manager 'CLUSQM2' during the log replay phase.
Log replay for queue manager 'CLUSQM2' complete.
Transaction manager state recovered for queue manager 'CLUSQM2'.
The Queue Manager ended for reason 276849192 ''
It did generate FDC and that shows me as
|Probe Type :- MSGAMQ9508 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9508: Program cannot connect to the queue manager.
|Comment1 :- CLUSQM2 |
| |
| Comment2 :- MQRC_Q_MGR_NOT_AVAILABLE
In the MQ error logs it reports as :
----- amqxfdcp.c : 815 --------------------------------------------------------
10/19/2010 12:37:31 - Process(6656.1) User(MUSR_MQADMIN) Program(amqrrmfa.exe)
Host(LBLRW04CZYB3BS)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager '' failed with reason code 0.
ACTION:
Ensure that the queue manager is available and operational.
----- amqxfdcp.c : 777 --------------------------------------------------------
10/19/2010 12:37:31 - Process(6656.1) User(MUSR_MQADMIN) Program(amqrrmfa.exe)
Host(LBLRW04CZYB3BS)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager CLUSQM2.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 6656.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the WMQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 815 --------------------------------------------------------
I am using MQ 7.0.1.2 version.
Any inputs appriciated to get the queue manager started. |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Tue Oct 19, 2010 2:33 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Looks serious. Can you paste the all the header info from the .FDC file?
_________________
Glenn |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 19, 2010 4:54 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
While I agree that it looks serious, the big question on the front of my mind when dealing with Windows is always...
Did you reboot after installing MQ?
The IBM MQSeries Service may need to start up in a fairly specific order, such that a simple start of the service from the control panel after install may not actually give a full and really functioning setup. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Oct 20, 2010 6:59 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| mqjeff wrote: |
While I agree that it looks serious, the big question on the front of my mind when dealing with Windows is always...
Did you reboot after installing MQ?
The IBM MQSeries Service may need to start up in a fairly specific order, such that a simple start of the service from the control panel after install may not actually give a full and really functioning setup. |
Hi Jeff,
I've been playing with 7.0.1.3 and doing lots of 7.0.1.0 installs / fixpack 3 installs / uninstalls on a Windows server without rebooting. I ensure the MQ service starts and stops at the the appropriate times. It all works fine.
The quick beginnings says a reboot is only required if any files were found to be "in use" during the fixpack install and the user elects to allow a reboot to fix this issue.
_________________
Glenn |
|
| Back to top |
|
|
| Praveensc |
| Posted: Thu Oct 21, 2010 1:09 am Post subject: |
|
|
Novice
Joined: 27 Feb 2008
Posts: 23
|
I had installed MQ 3 months back. Other queue managers are working fine. However.. after i reboot physical machine after creating the new queue manager, it got resolved. queue manager is up and running now.
Thanks for all your inputs but still could not find a reason why that was not starting without reboot of physical machine...!! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 21, 2010 1:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| gbaddeley wrote: |
Hi Jeff,
I've been playing with 7.0.1.3 and doing lots of 7.0.1.0 installs / fixpack 3 installs / uninstalls on a Windows server without rebooting. I ensure the MQ service starts and stops at the the appropriate times. It all works fine.
The quick beginnings says a reboot is only required if any files were found to be "in use" during the fixpack install and the user elects to allow a reboot to fix this issue. |
Hi Glenn - Sure, but if there's at all any problem after an install, the first thing I'm going to do is reboot and then retry. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Oct 21, 2010 4:35 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
If it's Windows my automatic reaction is to give it the three-fingered salute 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 21, 2010 4:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| exerk wrote: |
| If it's Windows my automatic reaction is to give it the three-fingered salute |
With Windoze:
When in doubt, reboot.
When not in doubt, reboot.
When it's all going fine & has been going fine for a few weeks, reboot.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Oct 21, 2010 5:06 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| And if it is important of of any value at all of any kind, don't use windows as a server. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Oct 21, 2010 3:07 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| mqjeff wrote: |
| ... but if there's at all any problem after an install, the first thing I'm going to do is reboot and then retry. |
I actually agree with you 
I am working on a silent MQ build that will roll out to dozens of new production Windoze servers. The builders won't be very impressed if I state in the doc to "try a reboot" if there are any problems during the install. MQ (and Windoze) has to be more reliable and predictable than that.
_________________
Glenn |
|
| Back to top |
|
|
|
|
