| Author |
Message
|
| satishnagarathnam |
 Posted: Fri Dec 05, 2003 3:00 am Post subject: AMQ6209: An unexpected asynchronous signal in AIX |
 |
|
Novice
Joined: 05 Dec 2003
Posts: 11
|
Hi , Can anyone give me a solution and reason for this error. I am Using Websphere MQ 5.3 an AIX environment.......!!
AMQ6209: An unexpected asynchronous signal (1 : SIGHUP) has been received and ignored. 
EXPLANATION:
Process 42590 received an unexpected asynchronous signal and ignored it. Thishas not caused an error but the source of the signal should be determined as it is likely that the signal has been generated externally to WebSphere MQ.
ACTION:
Determine the source of the signal and prevent it from re-occurring.
I have also the FDC attached ..
WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Friday December 05 09:44:03 UTC 2003 |
| Host Name :- europa_mer2 (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000007 (mercqa) |
| Program Name :- runmqsc |
| Process :- 00042590 |
| QueueManager :- EM2BRKR02 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6209: An unexpected asynchronous signal (2 : |
| SIGINT) has been received and ignored. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 2 2 |
| Arith2 :- 42590 a65e |
| Comment1 :- SIGINT |
| |
| |
+-----------------------------------------------------------------------------+
| ========================================= |
| |
| Date/Time :- Friday December 05 10:26:35 UTC 2003 |
| Host Name :- europa_mer2 (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC307040 |
| Application Name :- MQM |
| Component :- xlsRequestMutex |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000214 (mercqa) |
| Program Name :- launcher |
| Process :- 00104218 |
| Thread :- 00000001 |
| QueueManager :- EM2BRKR02 |
| Major Errorcode :- xecL_W_LONG_LOCK_WAIT |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6150 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6150: WebSphere MQ semaphore is busy. |
| FDCSequenceNumber :- 0
Please help to find a solution for this
Thanks and Regards
N.satish
_________________
N.Satish |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri Dec 05, 2003 6:09 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
Regarding XC338001:
| Quote: |
| The most likely cause of the XC338001 FFSTs is a user ( or the system at shutdown time) sending a SIGTERM to an MQ process, probably by issuing the kill command (for example kill -15 PID, where PID is the process ID of the MQ process creating the FFST). The asynchronous signal actually received by the process is recorded in the Arith1 field in the FFST. |
Regarding XC307040, see http://www-1.ibm.com/support/docview.wss?uid=swg21104588 |
|
| Back to top |
|
|
| satishnagarathnam |
| Posted: Mon Dec 15, 2003 3:27 am Post subject: An unexpected asynchronous signal (1 : SIGHUP) |
|
|
Novice
Joined: 05 Dec 2003
Posts: 11
|
Hi Bower
Thanks for the reply.
I am getting this error, when ever i am running runmqsc command on the queue manager. I am unable to execute any commands (e.g DISPLAY). It is hanging. What is the solution for this? Is there any FIXPACK avaiable for this !!
Please give the suggestion !!
Thanks and Regards
_________________
N.Satish |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Jan 14, 2004 7:26 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Satish,
are using MQ clustering? (not h/w HACMP clustering)
If yes, you might try asking IBM about pmr1908 (currently open on Solaris MQ 5.3 CSD4).
We also had this runmqsc hanging...
Michael |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Jan 14, 2004 9:30 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
the full pmr number is 01908,411,788 and fixes a problem introduced in CSD3 when fixing defect 7223 hung amqrrmfa.
If you are not on 5.3 CSD3 or above then this is not the problem you are looking at... 
Michael |
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Jan 15, 2004 2:02 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
You are running ga2 code (Fixpack 01 level - Who mentioned CSD...!), so the very first thing I would try is applying some maintenance (fixpack 4 or fixpack 5 would be sensible).
When does the fdc's get cut - is it when you run 'runmqsc', or when you terminate it because it is hung? If the second, its what I would expect.
The long_lock_wait fdc looks wrong though, but that is a different app (launcher?).
Note runmqsc does an MQCONN at startup, so do other apps work ok aside from runmqsc? |
|
| Back to top |
|
|
|
|
