Author |
Message
|
Pats21 |
Posted: Tue Nov 27, 2007 6:07 am Post subject: [SOLVED] QM ending Premtively |
|
|
Disciple
Joined: 08 Sep 2006 Posts: 154
|
Hi All,
We are using MQ v6.0.0.0 on AIX v5.3.
We are getting this weired problem where the QM is ending Preemtively.
when we start the QM it starts successfully but after few seconds it ends premtively .. ...
below are the log file and the FDC files
Any help is appreciated ...
************** FDC *****************
| PIDS :- 5724H7201 |
| LVLS :- 6.0.0.0 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- ZF095010 |
| Application Name :- MQM |
| Component :- zfuCacheAuthQueue |
| SCCS Info :- cmd/oam/amqzfuma.c, 1.86 |
| Line Number :- 944 |
| Build Date :- May 19 2005 |
| CMVC level :- p000-L050519 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000202 (mqm) |
| Program Name :- amqzfuma |
| Addressing mode :- 64-bit |
| Process :- 381088 |
| Thread :- 1 |
| QueueManager :- BRKRST_QM |
| ConnId(2) QM :- 3 |
| Major Errorcode :- MQRC_ENVIRONMENT_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ07DC |
| Probe Severity :- 4 |
| Probe Description :- AMQ6090: WebSphere MQ was unable to display an error |
| message 7DC. |
| FDCSequenceNumber :- 0
***********************************************************
********************* AMQERR01.LOG ******
11/27/07 19:01:27 - Process(393288.1) User(mqm) Program(amqzxma0_nd)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
BRKRST_QM.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 393288.
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.
----- amqxfdcx.c : 810 --------------------------------------------------------
11/27/07 19:01:27 - Process(393288.1) User(mqm) Program(amqzxma0_nd)
AMQ5008: An essential WebSphere MQ process 381088 (amqzfuma) 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 : 6446 -------------------------------------------------------
11/27/07 19:01:27 - Process(393288.1) User(mqm) Program(amqzxma0_nd)
AMQ5008: An essential WebSphere MQ process 479528 (amqrrmfa) 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.
----- amqxfdcx.c : 771 --------------------------------------------------------
11/27/07 19:01:27 - Process(393288.1) User(mqm) Program(amqzxma0_nd)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
BRKRST_QM.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 393288.
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.
----- amqxfdcx.c : 810 --------------------------------------------------------
11/27/07 19:01:27 - Process(393288.1) User(mqm) Program(amqzxma0_nd)
AMQ5008: An essential WebSphere MQ process 479528 (amqrrmfa) 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 -------------------------------------------------------
***************************************************
Also we were planning to install the fix pack 6.0.2
but if fails saying
**********************
You seem to have an MQ queue manager still running.
You must stop all MQ processing, and stop the Queue
Manager(s) by using the endmqm command before trying to
install/update/delete the MQ product.
**********************
However there are no processses running, we checked this using the cmds
"ps -ef | grep mqm" and "ps -ef | grep amq"
Regards,
Pats ....
Last edited by Pats21 on Tue Nov 27, 2007 7:25 am; edited 1 time in total |
|
Back to top |
|
 |
Vitor |
Posted: Tue Nov 27, 2007 6:24 am Post subject: Re: QM ending Premtively |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Pats21 wrote: |
| Major Errorcode :- MQRC_ENVIRONMENT_ERROR |
| Minor Errorcode :- OK | |
I'd ensure you have all the requirements for 64-bit correctly set (I notice your addressing mode is 64 bit) and all the permissions are set up correctly.
I'd also use something other than v6.0.0.0. Use v6.0.1 as a minimum and seriously consider v6.0.2 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Nov 27, 2007 6:25 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
check by trying to start the qmgr. It will tell you the offending process.
Stop the qmgr after that and clear shared memory (amqiclen) then attempt the reload of the fix pack.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
Pats21 |
Posted: Tue Nov 27, 2007 6:59 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006 Posts: 154
|
Hi,
thanks for your reply ...
we have done amqiclen and tried to start the QM .. but of no use ...
when we are trying to start the QM it is not showing any process that is offending ... it logs the same message as above in the log files ...
Also i am not sure what are the exact settings that needs to be done for 64-bit machine ... and also the permissions required ... it would be great if you can throw some more light on it ...
Pats ... |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Nov 27, 2007 7:04 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Pats21 wrote: |
Hi,
thanks for your reply ...
we have done amqiclen and tried to start the QM .. but of no use ...
when we are trying to start the QM it is not showing any process that is offending ... it logs the same message as above in the log files ...
Also i am not sure what are the exact settings that needs to be done for 64-bit machine ... and also the permissions required ... it would be great if you can throw some more light on it ...
Pats ... |
Check the quick beginnings manual for your platform.
Make sure all the kernel parameters have been set accordingly and some do require a restart of the box even in UNIX.
Check that the qmgr has enough file space to function:
(log file < 75% occupied, /var/mqm with enough free space etc...)
Search the forum (Solaris 10 with more than 4 qmgrs...)
And if loading maintenance on Windows use the Files in use parameter...
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
Pats21 |
Posted: Tue Nov 27, 2007 7:24 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006 Posts: 154
|
|
Back to top |
|
 |
nagabhb |
Posted: Mon Jun 18, 2012 8:31 am Post subject: |
|
|
Apprentice
Joined: 20 Dec 2010 Posts: 42
|
|
Back to top |
|
 |
Vitor |
Posted: Mon Jun 18, 2012 8:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
After 5 years I'm not surprised.
nagabhb wrote: |
We are facing the same issue. |
If you're facing exactly the same issue (i.e. on the same version of the software which was old when the OP was using it 5 years ago) then I think I've found your problem. Especially as....
nagabhb wrote: |
Can you provide more information on how it was resolved. |
... the OP refers to "applying the fixpack". I'd consider moving to WMQv7 and seeing if the problem persists. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|