| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Major Errorcode : arcE_XAER_PROTO |
« View previous topic :: View next topic » |
| Author |
Message
|
| sumantony@gmail.com |
 Posted: Wed Mar 14, 2007 7:53 am Post subject: |
 |
|
Newbie
Joined: 13 Mar 2007
Posts: 2
|
This issue 
I'm getting the following in FDC files on one of my queue managers:
WebSphere MQ First Failure Symptom Report
| ========================================= |
|
| Date/Time :- Wednesday February 08 10:57:36 EST 2006 |
| Host Name :- fairway (AIX 5.2)
| PIDS :- 5724B4101
| LVLS :- 530.12 CSD12
| Product Long Name :- WebSphere MQ for AIX
| Vendor :- IBM
| Probe Id :- AT040010
| Application Name :- MQM
| Component :- atxClose
| Build Date :- Dec 8 2005
| CMVC level :- p530-12-L051208
| Build Type :- IKAP - (Production)
| UserID :- 00000317 (mqm)
| Program Name :- amqzlaa0_nd
| Process :- 00037498
| Thread :- 00000130
| QueueManager :- UTCQ
| 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 :- 0
Looking at the WebLogic logs on my Solaris client, I see:
####<Feb 8, 2006 11:00:09 AM EST> <Error> <JTA> <rough> <comaqa> <ExecuteThread: '3' for queue: 'weblogic.ejb20.internal.JMSMe
ssagePoller'> <<WLS Kernel>> <BEA1-0042F639007DF610D7DF> <BEA-110412> <Name=JMSMessagePoller.nsRTRMDB,Xid=BEA1-0042F639007DF61
0D7DF(21589954),Status=Rolled back. [Reason=Unknown],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,s
econds since begin=30,seconds left=299,activeThread=Thread[ExecuteThread: '3' for queue: 'weblogic.ejb20.internal.JMSMessagePo
ller',5,Thread Group for Queue: 'weblogic.ejb20.internal.JMSMessagePoller'],XAServerResourceInfo[weblogic.ejb20.JMSConnectionP
oller.nsRTRMDB]=(ServerResourceInfo[weblogic.ejb20.JMSConnectionPoller.nsRTRMDB]=(state=rolledback,assigned=comaqa),xar=weblog
ic.deployment.jms.WrappedXAResource_com_ibm_mq_MQXAResource@8b6483,re-Registered = false),SCInfo[utcsqadomain+comaqa]=(state=r
olledback),properties=({weblogic.transaction.name=JMSMessagePoller.nsRTRMDB}),OwnerTransactionManager=ServerTM[ServerCoordinat
orDescriptor=(CoordinatorURL=comaqa+rough.domain.com:port+utcsqadomain+t3+, XAResources={weblogic.ejb20.JMSConnectionPol
ler.ErrorListenerBean, weblogic.ejb20.JMSConnectionPoller.nsEMMDB, weblogic.ejb20.JMSConnectionPoller.nsALMDB, weblogic.ejb20.
JMSConnectionPoller.nsPRMDB, weblogic.ejb20.JMSConnectionPoller.nsRTRMDB, JMS_nsMSGServer_NotDurable, weblogic.ejb20.JMSConnec
tionPoller.nsFXMDB},NonXAResources={})],CoordinatorURL=comaqa+rough.domain.com:port+utcsqadomain+t3+) completed heuristi
cally: (weblogic.ejb20.JMSConnectionPoller.nsRTRMDB, HeuristicHazard, (javax.transaction.xa.XAException: XA operation failed,
see errorCode)) >
####<Feb 8, 2006 11:00:09 AM EST> <Error> <EJB> <rough> <comaqa> <ExecuteThread: '3' for queue: 'weblogic.ejb20.internal.JMSMe
ssagePoller'> <<WLS Kernel>> <> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing
by a message-driven bean: javax.transaction.SystemException: Heuristic hazard: (weblogic.ejb20.JMSConnectionPoller.nsRTRMDB, H
euristicHazard, (javax.transaction.xa.XAException: XA operation failed, see errorCode))
The exception is : javax.transaction.SystemException: Heuristic hazard: (weblogic.ejb20.JMSConnectionPoller.nsRTRMDB, Heuristi
cHazard, (javax.transaction.xa.XAException: XA operation failed, see errorCode))
at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:384)
at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:350)
at weblogic.ejb20.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:307)
at weblogic.ejb20.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:336)
at weblogic.ejb20.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:452)
at weblogic.ejb20.internal.JMSMessagePoller.execute(JMSMessagePoller.java:468)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) |
|
| Back to top |
|
 |
| Toronto_MQ |
| Posted: Wed Mar 14, 2007 8:02 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
You need to ask BEA for the fix(es).
If it helps, the fixes we were given were:
CR253284 for the AT040010 FDC;
and
CR269661 for the heuristic condition.
Both had to be applied on the WLS side.
Steve |
|
| Back to top |
|
|
| rahoor |
| Posted: Thu May 03, 2007 5:43 am Post subject: CR253284 |
|
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
| Toronto_MQ wrote: |
You need to ask BEA for the fix(es).
If it helps, the fixes we were given were:
CR253284 for the AT040010 FDC;
and
CR269661 for the heuristic condition.
Both had to be applied on the WLS side.
Steve |
I am also seeing the same issues on 6.0.2.0 MQ and WL server, but can not find any references to CR253284 on weblogic web site, just CR269661.
Can anyone point me to the online reference for CR253284 please?
thanks |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
