| Author |
Message
|
| rbean |
 Posted: Wed Mar 17, 2004 11:29 am Post subject: xecE_W_UNEXPECTED_ASYNC_SIGNAL |
 |
|
Newbie
Joined: 08 Oct 2003
Posts: 6
|
Hi,
Our AIX server gets these intermitten internal MQ error and causes channels to go into retry. Are these unexpected signal errors avoidable?
Thanks for any help on this...
WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Friday March 12 15:05:45 EST 2004 |
| Host Name :- rsharry (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC267011 |
| Application Name :- MQM |
| Component :- xehAsySignalMonitor |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000253 (mqm) |
| Program Name :- amqcrsta_nd |
| Process :- 01073264 |
| 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 :- 14 e |
| Arith2 :- 1073264 106070 |
| Comment1 :- SIGALRM |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xehAsySignalMonitor
xcsFFST
MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xehAsySignalMonitor
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xcsFFST
Component Dumps (Thread 00000002) |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Mar 17, 2004 11:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is this APAR IY44839?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kman |
| Posted: Wed Mar 17, 2004 11:49 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
| That APAR is included in CSD05. rbean is already in CSD06. Must be a different set of reasons. |
|
| Back to top |
|
|
| kman |
| Posted: Thu Mar 18, 2004 12:12 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
Take a closer look into the AMQERR01.LOG and see what is recorded with respect to the communication with the other end. This could be associate with the channel problem - maybe network is not stable, or there is network probes sending signals out.
Try to check if there is network monitoring or some sort of sniffer around. |
|
| Back to top |
|
|
| akamal1 |
| Posted: Tue Apr 19, 2005 5:15 am Post subject: |
|
|
Newbie
Joined: 19 Apr 2005
Posts: 1
|
Hi
I am rbean's collegue and just wanted to ask this again.
We get one FDC ( same as posted above by rbean ) every 24 minutes.
Is any one else getting these errors and any ideas?
Our configuration: AIX 5.1/MQ5.3 with CSD5
Thanks for your help
Ahmed |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue Apr 19, 2005 6:28 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The FFST is saying that a source external to WMQ has issued a signal 14 to the amqcrsta proces, and the signal has been ignored. The FFST does not cause the channel to go into retry.
I suggest you find out what is happening on your machine every 24 minutes; maybe some cron job? |
|
| Back to top |
|
|
|
|
