| Author |
Message
|
| MQAltaf |
 Posted: Fri Jan 04, 2008 3:26 am Post subject: SIGDANGER error being reported in FDC |
 |
|
Centurion
Joined: 10 Feb 2005
Posts: 119
|
Hi,
I am seeing the following error in the MQ logs: -
----- amqxfdcx.c : 768 --------------------------------------------------------
04/01/08 11:08:02 - Process(1241242.2) User(mqm) Program(amqzlaa0_nd)
AMQ6209: An unexpected asynchronous signal (33 : SIGDANGER) has been received
and ignored.
EXPLANATION:
Process 1241242 received an unexpected asynchronous signal and ignored it. This
has 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.
----- amqxfdcx.c : 768 --------------------------------------------------------
The following FDC is also cut: -
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Friday January 04 10:44:25 GMT 2008 |
| Host Name :- ca11tepwasprd (AIX 5.3) |
| PIDS :- 5724H7201 |
| LVLS :- 6.0.2.0 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC267011 |
| Application Name :- MQM |
| Component :- xehAsySignalMonitor |
| SCCS Info :- lib/cs/unix/amqxerrx.c, 1.214.1.4 |
| Line Number :- 3029 |
| Build Date :- Sep 21 2006 |
| CMVC level :- p600-200-060921 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000125 (mqm) |
| Program Name :- amqzlaa0_nd |
| Addressing mode :- 64-bit |
| Process :- 1241242 |
| Thread :- 2 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6209: An unexpected asynchronous signal (33 : |
| SIGDANGER) has been received and ignored. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 33 21 |
| Arith2 :- 1241242 12f09a |
| Comment1 :- SIGDANGER |
| |
+-----------------------------------------------------------------------------+
$ dspmqver
Name: WebSphere MQ
Version: 6.0.2.0
CMVC level: p600-200-060921
BuildType: IKAP - (Production)
I believe the problem is related to paging size but am not sure how to set/increase this. Any suggestions would be appreciated
Thanks in advance |
|
| Back to top |
|
 |
| MQAltaf |
| Posted: Fri Jan 04, 2008 3:27 am Post subject: |
|
|
Centurion
Joined: 10 Feb 2005
Posts: 119
|
| As a result of the above, a Java application running under WAS grinds to a halt. The Java application used MQ as its transport mechanism |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Jan 04, 2008 4:37 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| MQAltaf |
| Posted: Fri Jan 04, 2008 6:14 am Post subject: |
|
|
Centurion
Joined: 10 Feb 2005
Posts: 119
|
Hi,
Thanks for the response.
It looks as though the Java application has a memory leak as it grinds to a halt over time. When the server is bounced all clears up. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jan 04, 2008 7:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| MQAltaf wrote: |
Hi,
Thanks for the response.
It looks as though the Java application has a memory leak as it grinds to a halt over time. When the server is bounced all clears up. |
Does it correctly release connections?? / JMS resources ??
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Sep 14, 2010 3:47 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I am getting similar problem.
How can I display the memory and page space being used by MQ processes (on AIX)? |
|
| Back to top |
|
|
|
|
