| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| FDC Error (XC338001) |
« View previous topic :: View next topic » |
| Author |
Message
|
| MQ_MQSI_User |
 Posted: Thu Jul 11, 2002 6:28 am Post subject: FDC Error (XC338001) |
 |
|
Novice
Joined: 11 Jul 2002
Posts: 20
Location: Charlotte, NC
|
I keep getting the following MQ FDC Error in the /var/mqm/errors directory on AIX 5.1 platform. Can anyone shed some light on this or get me pointed in the right direction. The environment is WCS (Websphere Commerce Suite) using Java binding to put messages to the queue on mq 5.2.1...any ideas...
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Wednesday July 10 21:10:41 CDT 2002 |
| Host Name :- integration_staging (AIX 5.1) |
| PIDS :- 5765B73 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for AIX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Nov 7 2000 |
| CMVC level :- p000-L001106 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000202 (mqm) |
| Program Name :- amqzlaa0_nd |
| Process :- 00011580 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6209: An unexpected asynchronous signal (15) has |
| been received and ignored. |
| Arith1 :- 15 f |
| Arith2 :- 11580 2d3c |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Wednesday July 10 21:10:43 CDT 2002 |
| Host Name :- integration_staging (AIX 5.1) |
| PIDS :- 5765B73 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for AIX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Nov 7 2000 |
| CMVC level :- p000-L001106 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000202 (mqm) |
| Program Name :- amqhasmx |
| Process :- 00016002 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6209: An unexpected asynchronous signal (15) has |
| been received and ignored. |
| Arith1 :- 15 f |
| Arith2 :- 16002 3e82 |
| |
| ===================================== |
| |
| Date/Time :- Wednesday July 10 21:10:48 CDT 2002 |
| Host Name :- integration_staging (AIX 5.1) |
| PIDS :- 5765B73 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for AIX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Nov 7 2000 |
| CMVC level :- p000-L001106 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000202 (mqm) |
| Program Name :- runmqchi |
| Process :- 00017076 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6209: An unexpected asynchronous signal (15) has |
| been received and ignored. |
| Arith1 :- 15 f |
| Arith2 :- 17076 42b4 |
| |
+-----------------------------------------------------------------------------+
They all pretty much refer to the same problem, xehAsySignalHandler.
_________________
MQSeries, MQSI |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Thu Jul 11, 2002 7:07 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well Signal 15 is from a kill process
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Jul 11, 2002 8:47 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I checked out an internal database and found the following:
The FDCs you sent show that the Channel Initiator (runmqchi) received an asynchronous signal and MQSeries ignored it. Because of signal handling changes in MQ this particular FDC (with Probe XC338001) is purely informational. It simply states that a signal was sent but we will not take any action on it. We write the FDC so that we have some indication that a process is being sent signals as this may be important in understanding a problem, but the FDC by itself is not reporting an actual problem, only a condition. This particular FDC is well known and occurs on a variety of platforms.
Unless you are seeing something else, I'd say that you can safely ignore the FDCs. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
