One of our support teams is having an issue where our MQ application abends while performing a MCCONN call . The test first starts the MQ application and shortly after that it starts the MQ manager. The MQ application tries to connect to MQ calling MQCONN at regular intervals until the MQCONN is successful. Occasionaly though (rough esitimate: 1 test run out of 20), the MQ application abends during an MQCONN call in this test. It looks to us that when the abend happens, it is just at the time when the MQ manager actually becomes available (ie., not during one of the many calls while the MQ manager is actually still down).
An FDC file is created. The header is as follows :-
WebSphere MQ First Failure Symptom Report
| =========================================
|
| Date/Time :- Thursday November 03 16:54:08 NFT 2005
| Host Name :- dev (AIX 5.2)
| PIDS :- 5724B4101
| LVLS :- 530.6 CSD06
| Product Long Name :- WebSphere MQ for AIX
| Vendor :- IBM
| Probe Id :- XC130003
| Application Name :- MQM
| Component :- xehExceptionHandler
| Build Date :- Feb 11 2004
| CMVC level :- p530-06-L040211
| Build Type :- IKAP - (Production)
| UserID :- 00000261 (citmq)
| Program Name :- mqconntest
| Process :- 00024454
| Thread :- 00000001
| QueueManager :- C05_SNL4_MQM
| Major Errorcode :- STOP
| Minor Errorcode :- OK
| Probe Type :- HALT6109
| Probe Severity :- 1
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred.
| FDCSequenceNumber :- 0
| Arith1 :- 11 b
| Comment1 :- SIGSEGV
I have checked this site and can see some good information about the SIGSERV / XC130003 error. We have changed the AMQ_ABORT_ON_EXCEPTION variable to be TRUE, however no CoreDump was created after the latest FDC.
There was an errpt file which showed the following
===============================================
LABEL: AMQFFST1
IDENTIFIER: 813FE820
Date/Time: Thu Nov 3 16:54:08 NFT
Sequence Number: 1278019
Machine Id: 000928804C00
Node Id: dev
Class: S
Type: UNKN
Resource Name: MQSeries NONE
Description
SOFTWARE PROGRAM ERROR
Probable Causes
UNDETERMINED
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
REVIEW DETAILED DATA
CONTACT APPROPRIATE SERVICE REPRESENTATIVE
Detail Data
DETECTING MODULE
xehExceptionHandler
SOFTWARE ERROR CODE
0000 0003
FILE NAME
/var/mqm/errors/AMQ24454.0.FDC
================================================
So before i go to MQ support i thought id see if anyone had encountered a similar issue(s)
Im after a response to
- Why the MQ application would fail on random occasions ?
- Why no Coredump would be created even with the variable set to 'true' ?
I think this is probably to do with the code we have written but any help would be appreciated
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