| Author |
Message
|
| gunter |
 Posted: Thu Jan 12, 2006 6:04 am Post subject: FDC Probe Id XC035021 |
 |
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
Hi,
today I found a FDC reported in /var/mqm/error. Apart from this FDC and the related entry in errpt and AMQERR01.LOG, nothing happend. Ther is no error message from the clients, no process is restarted, even the reported amqzlaa0_nd is still running.
I found a few posts with this ProbeId, but the problems were on older systems and related to java. We use Websphere MQ 5.3 CSD07 on AIX 5.3. We don't use java, but there is Tivoli running and I don't know if it connects to the queuemanager.
The system is running for month and I've never seen this. Does anybody know what it is ?
| Quote: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday January 12 09:50:50 NFT 2006 |
| Host Name :- aix756897(AIX 5.3) |
| PIDS :- 5724B4101 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC035021 |
| Application Name :- MQM |
| Component :- xcsCreateThread |
| Build Date :- May 27 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000203 (mqm) |
| Program Name :- amqzlaa0_nd |
| Process :- 00068116 |
| Thread :- 00000001 |
| QueueManager :- AIX756897 |
| Major Errorcode :- xecP_E_NO_RESOURCE |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
|
| Quote: |
01/12/06 09:50:50
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 0. This message is issued in
association with other messages.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 673 --------------------------------------------------------
01/12/06 09:50:50
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
AIX756897.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 68116.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 707 --------------------------------------------------------
|
Thanks
Gunter
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Jan 12, 2006 6:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What ML of AIX 5.3 are you on?
Are you running out of memory?
What is the nofiles limit for the mqm user in /etc/security/limits?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| gunter |
| Posted: Thu Jan 12, 2006 6:32 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
oslevel is 5.3.0.0
nofiles is 2000
The system is not out of memory.
The process amqzlaa0 -mSV0410570 -fip0 was grown to nearly 150MB until the 6., after a system crash and new startup it is only 8Kb.
There are only 10 to 20 applications using client connection, the rest( ~400) uses bindings.
Thanks
Gunter
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 12, 2006 6:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Again, what is the nofiles limit for the mqm user in /etc/security/limits?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| gunter |
| Posted: Thu Jan 12, 2006 6:39 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
There is no special entry for mqm, default is 2000.
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 12, 2006 6:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The Quick Beginnings Guide for AIX recommends a setting of 10,000.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| gunter |
| Posted: Thu Jan 12, 2006 7:11 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
Thank you for the quick response. It's defenitly a good idea to follow this recommodation. But I miss the error 2195 in the FDC and/or AMQERR01.LOG.
By reading the Guide, I found the chapter 'System Resource Limits', I believe it's not set, either.
Gunter
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Jan 12, 2006 7:52 am Post subject: Re: FDC Probe Id XC035021 |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
The same probeId can mean a shortage of memory or a failure to start a new thread in a reasonable period of time (I think "reasonable" means 10 seconds in this case).
It seems likely either way that a memory shortage can be a possible cause of this probeId. However if it's certain that you had plenty of available memory then sorry this appears not to be the explanation.
It may be worth opening a call and sending the FDC file(s) to Support to see if they have more of an idea. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 12, 2006 7:58 am Post subject: Re: FDC Probe Id XC035021 |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mvic wrote: |
The same probeId can mean a shortage of memory or a failure to start a new thread in a reasonable period of time (I think "reasonable" means 10 seconds in this case). |
I was assuming a failure to start a thread, given
| gunter wrote: |
| | Component :- xcsCreateThread | |
And then figuring that it might be a file descriptor limit that was preventing the thread from starting - based on the comments in the Quick Beginnings Guide.
It's probably not ever a bad idea to open a PMR when you have an FFST/FDC file thrown.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| gunter |
| Posted: Fri Jan 13, 2006 2:13 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
Hi,
I reviewed the 5.3 doku and could not find anything about limits, this is only documented in the version 6 manual. But I found a few hints in problem descriptions, that the default is to low.
Thanks for your help.
Gunter
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
|
|
