MQSeries.net :: View topic

Shalini · Posted: Wed Apr 06, 2005 2:56 am Post subject:

Hi All,

We are getting the following FDC with MQ5.3CSD9 AIX 5.1

+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday April 02 19:12:00 SAUST 2005 |
| Host Name :- JunkServer (AIX 5.1) |
| PIDS :- 5724B4101 |
| LVLS :- 530.9 CSD09 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC267011 |
| Application Name :- MQM |
| Component :- xehAsySignalMonitor |
| Build Date :- Dec 13 2004 |
| CMVC level :- p530-09-L041213 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000204 (mqadm) |
| Program Name :- runmqchi |
| Process :- 00061602 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 33 21 |
| Arith2 :- 61602 f0a2 |
| Comment1 :- SIGDANGER |
| |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
xehAsySignalMonitor
xcsFFST

MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xehAsySignalMonitor
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem

**********************************************
As per the search gives the following info....
Problem conclusion :
This problem has been fixed and the fix will be shipped in the following PTFs: WebSphere MQ V5.3 CSD05

Whenever a dynamic lpar configuration change is made (add/remove cpu's or add/remove memory), WebSphere MQ receives a signal 58(SIGRECONFIG) from AIX and issues the following FDC:

SIGRECONFIG is a benign signal from a WebSphere MQ perspective.
It should not need to take any action when this event is signaled. This signal should simply be added to the set of signals that
the asynchronous signal handler ignores.

Some other searches about the "SIGRECONFIG" gives me following informaion..

The SIGRECONFIG signal is sent to the applications at the various phases of dynamic logical partitioning.
The DR_RECONFIG_DONE flag is used when the application wants to notify the kernel that necessary action to adjust their use of resources has been taken in response to the SIGRECONFIG signal sent to them.

Let me know why this happenes and admin people has confirmed that they havenot done any configuration change in OS level...

My AMQERR01 on 10:14 and 10:20 are as above shows something like below

----- amqxfdcx.c : 688 --------------------------------------------------------
04/06/05 10:14:32
AMQ6184: An internal WebSphere MQ error has occurred on queue manager JUNKQMGR.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 44978.
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 : 722 --------------------------------------------------------
04/06/05 10:20:17
AMQ6125: An internal WebSphere MQ error has occurred.

EXPLANATION:
An internal error has occurred with identifier 20806024. This message is
issued in association with other messages.
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 : 688 --------------------------------------------------------
04/06/05 10:20:17
AMQ6184: An internal WebSphere MQ error has occurred on queue manager JUNKQMGR.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 61602.
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 : 722 --------------------------------------------------------

Please help