| Author |
Message
|
| ALCSALCS |
 Posted: Tue Sep 04, 2012 3:03 am Post subject: FDC occurring in LINUX system |
 |
|
Acolyte
Joined: 14 Apr 2002
Posts: 61
|
Running MQ 7.0.1.3 in Linux Red Hat and this problem started to happens
----- amqxfdcx.c : 822 --------------------------------------------------------
08/28/2012 12:16:44 AM - Process(17262.131) User(mqm) Program(amqzlaa0)
Host(labgcxs002p.resource.dcglobal.sita.aero)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 20807594. 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 any generated output files. Use either the WMQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcx.c : 783 --------------------------------------------------------
08/28/2012 12:16:44 AM - Process(17262.131) User(mqm) Program(amqzlaa0)
Host(labgcxs002p.resource.dcglobal.sita.aero)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
XS_BAGSMART.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 17262.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the WMQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcx.c : 822 -------
Header for the FDC is :
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Tue August 28 2012 00:16:44 GMT |
| UTC Time :- 1346113004.832458 |
| UTC Time Offset :- 0 (GMT) |
| Host Name :- labgcxs002p.resource.dcglobal.sita.aero |
| Operating System :- Linux 2.6.18-308.8.2.el5 |
| PIDS :- 5724H7230 |
| LVLS :- 7.0.1.3 |
| Product Long Name :- WebSphere MQ for Linux (x86-64 platform) |
| Vendor :- IBM |
| Probe Id :- AT041015 |
| Application Name :- MQM |
| Component :- atxStart |
| SCCS Info :- lib/lqm/amqatxca.c, 1.61.1.3 |
| Line Number :- 455 |
| Build Date :- Aug 31 2010 |
| CMVC level :- p701-7013TRIAL |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 10121 (mqm) |
| Real UserID :- 10121 (mqm) |
| Program Name :- amqzlaa0 |
| Addressing mode :- 64-bit |
| Process :- 17262 |
| Process(Thread) :- 23008 |
| Thread :- 131 |
| ThreadingModel :- PosixThreads |
| QueueManager :- XS_BAGSMART |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 292033 |
| ConnId(2) QM :- 19964 |
| Last HQC :- 2.5.5-4894328 |
| Last HSHMEMB :- 2.11.11-443032 |
| Major Errorcode :- arcE_XAER_PROTO |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 51 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
I am not familiar with FDC and how can I get further information
I googled IBM with Probe Id AT041015 and I found an old entry in the forum (February 2005) reporting the same FDC but with no answers.
Someone can help with extra information ? Otherwise I am planning to contact IBM
Any help will be appreciated |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Sep 04, 2012 3:14 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
You're back level in terms of maintenance so before raising a PMR you should think about applying the latest FixPack, especially in light of THIS.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 04, 2012 3:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So the Component suggests that the queue manager is attempting to start up the XA subsystems, and the arcE_XAER_PROTO suggests that the queue manager is having an issue connecting to the database involved in the XA configuration.
So I'd review your XA configuration and confirm that the database in question is available and can be reached from the queue manager machine.
And always open a PMR when you have an FDC. |
|
| Back to top |
|
|
| ALCSALCS |
| Posted: Tue Sep 04, 2012 10:47 pm Post subject: |
|
|
Acolyte
Joined: 14 Apr 2002
Posts: 61
|
| Many thanks for the information provided. |
|
| Back to top |
|
|
| Andyh |
| Posted: Wed Sep 05, 2012 11:33 pm Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
It's difficult to analyze this issue correctly based upon such a small extract from the FDC.
The queue manager has detected an XA protocol violation, due to an xa_start being issued in a thread of control which already has an active transaction association.
This error would typically be raised by the queue manager to warn of a problem in the transaction manager that is managing this transaction (MQ is a resource manager in this situation).
What is the transaction manager in this case ? Is the transaction manager one of those supported by MQ ? |
|
| Back to top |
|
|
| ALCSALCS |
| Posted: Thu Sep 06, 2012 12:40 am Post subject: |
|
|
Acolyte
Joined: 14 Apr 2002
Posts: 61
|
Many Thanks for the information.
I opened a PMR and provided the full information about FDC. |
|
| Back to top |
|
|
|
|
