| Author |
Message
|
| pshan81 |
 Posted: Fri Feb 27, 2009 11:15 pm Post subject: AMQ6209: An unexpected asynchronous signal (2) |
 |
|
Acolyte
Joined: 24 May 2005
Posts: 72
|
Hi,
We have MQ 5.3 CSD 10 installed on Aix 5.2 production machine (we are upgrading to 6.0.2.5 soon). The below FDC was generated yesterday and the applications were not able to GET or PUT messages from/to the queue.MQ didn't respond to dspmq and runmqsc commands.It was hung and we didn't get any reply.FFST shows the program name as runmqsc.
+------------------------------------------------------------------------|
| |
| WebSphere MQ First Failure Symptom Report |
|
|========================================|
| Date/Time :- Friday February 27 16:16:04 HKT 2009 |
| Host Name :- XXX (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.10 CSD10 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- May 12 2005 |
| CMVC level :- p530-10-L050504 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000205 (root) |
| Program Name :- runmqsc |
| Process :- 10473478 |
| 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 |
| Comment1 :- SIGINT |
+-----------------------------------------------------------------------+
We searched the probeid in ibm & mqseries.net. The cause stated is "The server was rebooted, without shutting down the queue manager".However, we didn't reboot the system. We resolved the issue by stopping all the adapters/applications using MQ.
Could other possible cause for the issue be some user issuing kill command to runmqsc? We tried to kill a runmqsc process in a development environment and couldn't get any FDC.What does the asyncsignal "Arith1 :- 2 2 SIGINT" mean?Could anyone help me to find the root cause for the issue. |
|
| Back to top |
|
 |
| exerk |
| Posted: Sat Feb 28, 2009 12:07 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Was the server memory/CPU bound at the time, before you killed a lot of processes? Are some of them not very well behaved, i.e. causing a max out on resources if waiting on a dependency?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Feb 28, 2009 12:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Try exiting runmqsc with a ctrl-Z instead of ctrl-D in Unix and you get a hung runmqsc session. You can use ps -ef to find the process and kill it.
Yeah I know... jumping between win MO72 and putty runmqsc will get you at times...
This use of ctrl-Z in Unix is one way I know of giving you an FDC like the one you stated.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| pshan81 |
| Posted: Sun Mar 01, 2009 8:52 pm Post subject: |
|
|
Acolyte
Joined: 24 May 2005
Posts: 72
|
| Quote: |
| Was the server memory/CPU bound at the time, before you killed a lot of processes? |
Exerk, Our system admin confirmed that the memory, CPU utilization & I/O was normal all through the day.
| Quote: |
| Try exiting runmqsc with a ctrl-Z instead of ctrl-D in Unix and you get a hung runmqsc session. |
We normally use ctrl-C if there is no response for a command.runmqsc was not responding even for ctrl-C.We killed all the runmqsc processes after using ps -ef|grep mqm command.
What does "AMQ6209: An unexpected asynchronous signal (2 : |
| SIGINT) has been received and ignored" mean?
Do we have to check with IBM? |
|
| Back to top |
|
|
| vol |
| Posted: Sun Mar 01, 2009 10:44 pm Post subject: |
|
|
Acolyte
Joined: 01 Feb 2009
Posts: 69
|
| signal 2 (SIGINT) is generated by the OS when a user presses ^C in an app. WMQ ignores the signal, and dumps an FFST saying that it has ignored it, giving the signal number. |
|
| Back to top |
|
|
| pshan81 |
| Posted: Sun Mar 01, 2009 11:38 pm Post subject: |
|
|
Acolyte
Joined: 24 May 2005
Posts: 72
|
| Quote: |
| WMQ ignores the signal, and dumps an FFST saying that it has ignored it, giving the signal number. |
But in our case runmqsc,dspmq & stop channel requests didn't respond.The control did not comeout even after pressing ctrl-C.MQ responded normally only after shutting down all applications, MQ channels and runmqsc processes.Even if someone issues a kill command to runmqsc, it should not stop processing other commands right?
Hope it has reached a state of panic or hung. |
|
| Back to top |
|
|
| pshan81 |
| Posted: Thu Mar 05, 2009 10:20 pm Post subject: |
|
|
Acolyte
Joined: 24 May 2005
Posts: 72
|
We are still analysing the root cause for the failure. During the analysis we found that "AMQ6209: An unexpected asynchronous signal (2 : SIGINT) has been received and ignored" error was accompanied by "AMQ6183: An internal WebSphere MQ error has occurred." However, there was no FDC file for AMQ6183.
The below link highlights that AMQ6183 can occur when runmqsc commands piped from echo into runmqadm -r cause WebSphere® MQ to hang.This happens for MQSC commands that produce a large amount of output.
http://www-01.ibm.com/support/docview.wss?uid=swg21162939
We use "echo piped with runmqsc command scripts" for queue & monitoring.Could this error occur for runmqsc also.Is it encountered only in supportpac? |
|
| Back to top |
|
|
|
|
