MQSeries.net :: View topic - internal Websphere MQ Error - failing process

phudak · Posted: Wed Apr 20, 2005 9:10 am Post subject:

Hi,

It looks like listener get probs...

can u help me solve it ?

04/17/05 06:47:28
AMQ6183: An internal WebSphere MQ error has occurred.

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

test:/var/mqm/errors$ps -ef | grep 15417
mqm 15417 1 18 Apr 17 ? 1:00 runmqlsr -m QMGR -t TCP -p 1415

+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sunday April 17 06:47:28 METDST 2005 |
| Host Name :- test (HP-UX B.11.11) |
| PIDS :- 5724B4102 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for HP-UX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Oct 21 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000104 (mqm) |
| Program Name :- runmqlsr_nd |
| Process :- 00015264 |
| 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 :- 1 1 |
| Arith2 :- 15264 3ba0 |
| Comment1 :- SIGHUP |
| |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
xehAsySignalMonitor
xehHandleAsySignal
xcsFFST

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

Component Dumps (Thread 00000002)
-------------------------------------

| Probe Type :- MSGAMQ6209

An unexpected asynchronous signal (&1) has been received and ignored

User response:
Determine the source of the signal and prevent it from occuring again

hm, SIGHUP ? SIGHUP as I remember is to refresh process( for example to reread configuration files)

i don't think it can be any strange unknown process which just send HUP to all acitve PID's

maybe it's internal MQ way of communication and signalHandler didn't expect it that time ?

thanks a lot

Peter Hudak