| Author |
Message
|
| AntonGolovin |
 Posted: Mon Jul 24, 2006 12:15 pm Post subject: Problem with MQ stability upon reboot... |
 |
|
Novice
Joined: 24 Jul 2006
Posts: 23
|
Hello, and thank you in advance for any help.
We have MQ 6.0 running on the box, which is an upgrade from MQ 5.3, and when we reboot the server, some queue managers run but are not connected to, and therefore inaccessible.
They show the green icon in MQ Explorer, but we cannot view the queues or anything else.
I was wondering if you could point to a source of possible solutions for this problem.
Thank you very much! |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jul 24, 2006 12:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What can't connect to them? MQExplorer? client applications? server applications?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| AntonGolovin |
| Posted: Mon Jul 24, 2006 12:19 pm Post subject: |
|
|
Novice
Joined: 24 Jul 2006
Posts: 23
|
| jefflowrey wrote: |
| What can't connect to them? MQExplorer? client applications? server applications? |
We are running some apps on WAS 6.0 which cannot connect to them in this case. Also, the MQ Explorer cannot connect to them. The conclusion we draw is that they are in general not connectable to, somehow, having something go wrong at the startup. If we manually start them, they start and connect fine, but the reboot does not start them all properly.
We were concerned about automating their startup. I am pretty much at my wit's end what could be the reason. |
|
| Back to top |
|
|
| AntonGolovin |
| Posted: Mon Jul 24, 2006 12:23 pm Post subject: |
|
|
Novice
Joined: 24 Jul 2006
Posts: 23
|
This is the error given, for instance, related to the queue manager, pixqmgr:
7/21/2006 11:21:38 - Process(3260.3) User(mqadmin) Program(amqmsrvn.exe)
AMQ7880: Error code 71 starting pixqmgr/Queue Manager WebSphere MQ service.
EXPLANATION:
The service was unable to start pixqmgr/Queue Manager. The error message
reported was as follows: WebSphere MQ queue manager 'pixqmgr' starting. 10 log
records accessed on queue manager 'pixqmgr' during the log replay phase. Log
replay for queue manager 'pixqmgr' complete. Transaction manager state
recovered for queue manager 'pixqmgr'. AMQ5615: Default objects cannot be
created: CompCode = 2 Reason = 2059.
ACTION:
Use WebSphere MQ Explorer to investigate why the service could not begin. If
recovery for this service is active, MQ will attempt to recover.
-------------------------------------------------------------------------------
7/21/2006 11:21:39 - Process(7648.1) User(mqadmin) Program(amqzxma0.exe)
AMQ5008: An essential WebSphere MQ process 7732 (amqrrmfa.exe) cannot be found
and is assumed to be terminated.
EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources. Some operating systems terminate processes to free resources. If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created.
ACTION:
WebSphere MQ will stop all MQ processes. Inform your systems administrator.
When the problem is rectified WebSphere MQ can be restarted.
----- amqxfdcp.c : 735 --------------------------------------------------------
7/21/2006 11:21:40 - Process(7648.1) User(mqadmin) Program(amqzxma0.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager pixqmgr.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 7648.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 773 --------------------------------------------------------
7/21/2006 11:21:40 - Process(7648.1) User(mqadmin) Program(amqzxma0.exe)
AMQ5008: An essential WebSphere MQ process 7732 (amqrrmfa.exe) cannot be found
and is assumed to be terminated.
EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources. Some operating systems terminate processes to free resources. If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created.
ACTION:
WebSphere MQ will stop all MQ processes. Inform your systems administrator.
When the problem is rectified WebSphere MQ can be restarted.
----- amqzxmb0.c : 6387 -------------------------------------------------------
7/21/2006 11:21:46 - Process(7724.1) User(mqadmin) Program(amqzmur0.exe)
AMQ6090: WebSphere MQ was unable to display an error message 7D9.
EXPLANATION:
MQ has attempted to display the message associated with return code hexadecimal
'7D9'. The return code indicates that there is no message text associated with
the message. Associated with the request are inserts 1 : 3 : STATISTICS : : .
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
7/21/2006 11:21:49 - Process(7724.1) User(mqadmin) Program(amqzmur0.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager pixqmgr.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 7724.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 773 --------------------------------------------------------
7/21/2006 11:34:10 - Process(5680.1) User(mqadmin) Program(amqzxma0.exe)
AMQ6118: An internal WebSphere MQ error has occurred (7064)
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 24, 2006 2:40 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
7/21/2006 11:21:39 - Process(7648.1) User(mqadmin) Program(amqzxma0.exe)
AMQ5008: An essential WebSphere MQ process 7732 (amqrrmfa.exe) cannot be found
and is assumed to be terminated.
EXPLANATION:
- 1) A user has inadvertently terminated the process.
- 2) The system is low on resources.
Some operating systems terminate processes to free resources. If your system is low on resources, it is possible it has terminated the process so that a new process can be created.
ACTION:
WebSphere MQ will stop all MQ processes. Inform your systems administrator.
When the problem is rectified WebSphere MQ can be restarted. |
How many qmgrs are you running on this box?
Specify box OS and MQ (versions, patches etc...)
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| AntonGolovin |
| Posted: Tue Jul 25, 2006 4:26 am Post subject: |
|
|
Novice
Joined: 24 Jul 2006
Posts: 23
|
| Good morning, thank you for your response. We are running nine queue managers on the MQ server with Windows 2003 Standard Server and MQ 6.0. |
|
| Back to top |
|
|
| PaperHouse |
| Posted: Tue Jul 25, 2006 5:05 am Post subject: |
|
|
Newbie
Joined: 18 Jul 2006
Posts: 8
Location: London
|
Unless you change the Heap size as described here:-
http://support.microsoft.com/kb/q184802/
I wouldn't run more than 4 queue managers on a server.
In the meantime you may be able to start the stopped queue managers from the command prompt. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Jul 25, 2006 5:31 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| AntonGolovin wrote: |
| We are running nine queue managers on the MQ server with Windows 2003 Standard Server and MQ 6.0. |
In my experience, I've seen a limit because of system resources right at 10 qmgrs. I'd suggest that you look at what you are doing and get a second machine if you are going to consistently have 9 qmgrs running. |
|
| Back to top |
|
|
| AntonGolovin |
| Posted: Wed Jul 26, 2006 6:02 am Post subject: |
|
|
Novice
Joined: 24 Jul 2006
Posts: 23
|
Hi, guys! We did increase heap size as suggested, but still some queue managers start but cannot be connected to at system reboot. We are running 7 queue managers (decreased the number to essential ones) on a box running Windows 2003 Standard, but the box also has several instances of DB2, WAS, and some apps.
Any assistance would be greatly appreciated. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jul 26, 2006 1:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| AntonGolovin wrote: |
Hi, guys! We did increase heap size as suggested, but still some queue managers start but cannot be connected to at system reboot. We are running 7 queue managers (decreased the number to essential ones) on a box running Windows 2003 Standard, but the box also has several instances of DB2, WAS, and some apps.
Any assistance would be greatly appreciated. |
Your box is still overloaded.
Get a box to serve MQ only with possibly a WAS instance (multiphase commit). Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
