| Author |
Message
|
| KramJ |
 Posted: Wed Feb 08, 2006 12:36 pm Post subject: Major Errorcode : arcE_XAER_PROTO |
 |
|
Voyager
Joined: 09 Jan 2006
Posts: 80
Location: Atlanta
|
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)
I'm not familiar with WebLogic. Do these errors indicate a communication error between WebLogic and MQ or are they indicating errors with the application that they developers need to look at? |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Wed Feb 08, 2006 12:43 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Try searching for the Probe Id AT040010 here:
http://www.ibm.com/support/us/
You may find a known issue.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Feb 08, 2006 3:41 pm Post subject: Re: Major Errorcode : arcE_XAER_PROTO |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| KramJ wrote: |
| I'm not familiar with WebLogic. Do these errors indicate a communication error between WebLogic and MQ or are they indicating errors with the application that they developers need to look at? |
This is a problem associated with the xa_close function call. This is one of a range of XA function calls that a transaction manager product will make into MQ. The data you've posted is MQ's record of the fact it thinks there is a "protocol error" in the sequence of calls it has received.
Please check to see if the machine is up to date with Weblogic fixes. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 08, 2006 7:30 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Most probably denotes an error in how the Transaction Manager handled a multiphase commit. Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Feb 09, 2006 1:28 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| fjb_saper wrote: |
| Most probably denotes an error in how the Transaction Manager handled a multiphase commit. Enjoy |
This is not the case, I'm afraid. xa_close is XA's equivalent of 'disconnect'. I have seen similar FDC reports on MQ<->Weblogic systems several times before. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 09, 2006 6:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mvic wrote: |
| fjb_saper wrote: |
| Most probably denotes an error in how the Transaction Manager handled a multiphase commit. Enjoy |
This is not the case, I'm afraid. xa_close is XA's equivalent of 'disconnect'. I have seen similar FDC reports on MQ<->Weblogic systems several times before. |
Sure but you woudn't get it with an FDC to boot.
If you hit it with the XAE_PROTO_ERR it means that the TM did issue a close after having issued a prepare but never issued the "end".
It has something to do with the TM sending the right XA command in the wrong sequence. This is why it is a protocol error, because the XA protocol specifies a sequence of events that was not respected.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Macjvi |
| Posted: Tue Feb 20, 2007 5:34 am Post subject: |
|
|
Newbie
Joined: 10 Jan 2006
Posts: 5
Location: Swizerland, Bern
|
up ! 
Hello evrybody !
I've got a similair problem ! We have BEA WLS installed on a server with
a MQ client (server A). The Aplication (WLS) try to make a global transaction with a Queue on a MQ server (server B).
On the server A (MQ client) i installed a MQ server version to be sure i have all the file i need to make a XA transaction (the file mqetclient.jar is only on the server version). Evrything is working fine, we can get message with WLS from the MQ server till we try to make the same thing with a global transaction !
<Feb 20, 2007 7:34:16 AM CET> <Error> <JTA> <BEA-110412> <Name=JMSMessagePoller.BuKBu_BucherServiceAsyncMDBean,Xid=BEA1-0009656032E120AC67FC(192547941)
,Status=Rolled back. [Reason=Unknown],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds left=59970
,activeThread=Thread[ExecuteThread: '9' for queue: 'ch.rtc.business.baseServices.kf.administration.bucher.BuKBu_BucherServiceAsyncQ',5,Thread Group for
Queue: 'ch.rtc.business.baseServices.kf.administration.bucher.BuKBu_BucherServiceAsyncQ'],XAServerResourceInfo[weblogic.ejb20.JMSConnectionPoller.BuKB
u_BucherServiceAsyncMDBean]=(ServerResourceInfo[weblogic.ejb20.JMSConnectionPoller.BuKBu_BucherServiceAsyncMDBean]=(state=rolledback,assigned=Kf_AppSer
ver1),xar=weblogic.deployment.jms.WrappedXAResource_com_ibm_mq_MQXAResource@b6bc3f5,re-Registered = false),SCInfo[x_kf_domain+Kf_AppServer1]=(state=rol
ledback),properties=({weblogic.transaction.name=JMSMessagePoller.BuKBu_BucherServiceAsyncMDBean}),OwnerTransactionManager=ServerTM[ServerCoordinatorDes
criptor=(CoordinatorURL=Kf_AppServer1+usv0403.rtc.ch:11001+x_kf_domain+t3+, XAResources={},NonXAResources={})],CoordinatorURL=Kf_AppServer1+usv0403.rtc
.ch:11001+x_kf_domain+t3+) completed heuristically: (weblogic.ejb20.JMSConnectionPoller.BuKBu_BucherServiceAsyncMDBean, HeuristicHazard, (javax.transac
tion.xa.XAException: XA operation failed, see errorCode)) >
<Feb 20, 2007 7:34:16 AM CET> <Error> <EJB> <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.BuKBu_BucherServiceAsyncMDBean, HeuristicHazard,
(javax.transaction.xa.XAException: XA operation failed, see errorCode))
The exception is : javax.transaction.SystemException: Heuristic hazard: (weblogic.ejb20.JMSConnectionPoller.BuKBu_BucherServiceAsyncMDBean, HeuristicHa
zard, (javax.transaction.xa.XAException: XA operation failed, see errorCode))
at weblogic.transaction.internal.ServerTransactionImpl.internalRollback()V(ServerTransactionImpl.java:398)
at weblogic.transaction.internal.ServerTransactionImpl.rollback()V(ServerTransactionImpl.java:364)
at weblogic.ejb20.internal.JMSMessagePoller.processOneMessage(Z)Z(JMSMessagePoller.java:305)
at weblogic.ejb20.internal.JMSMessagePoller.pollContinuously()V(JMSMessagePoller.java:334)
at weblogic.ejb20.internal.JMSMessagePoller.pollForParent()V(JMSMessagePoller.java:450)
at weblogic.ejb20.internal.JMSMessagePoller.execute(Lweblogic/kernel/ExecuteThread;)V(JMSMessagePoller.java:466)
at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
I have no FDC on MQ side just error on the WLS side...
We use MQ ver 6.0.2.0 "client" on Linux and Server on Solaris 8
One more thing ! (no no i'm not Steve Job...)
When we start the WLS Aplication we become also this error:
MQJE082: File containing the license unit information could not be found - run setmqcap
I don't understand because since ver 6 we don't need anymore setmqcap !!
So forgive me for my poor english (i speak french normally... nobody's is perfekt)
Thanks a lot for your help !
kind regards
Macjvi
_________________
MQSeries works on UNISYS OS2200 too !! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Feb 20, 2007 5:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You installed the Extended Transactional Client?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Macjvi |
| Posted: Tue Feb 20, 2007 6:01 am Post subject: |
|
|
Newbie
Joined: 10 Jan 2006
Posts: 5
Location: Swizerland, Bern
|
| jefflowrey wrote: |
| You installed the Extended Transactional Client? |
Is it "MQSeriesTXClient" ? when yes the answer is yes but if it is
something else..... oops
_________________
MQSeries works on UNISYS OS2200 too !! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Feb 20, 2007 6:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you don't know, then you didn't.
Talk to your IBM Sales Representative.
Or don't use XA over client connections.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Macjvi |
| Posted: Tue Feb 20, 2007 6:06 am Post subject: |
|
|
Newbie
Joined: 10 Jan 2006
Posts: 5
Location: Swizerland, Bern
|
| jefflowrey wrote: |
If you don't know, then you didn't.
Talk to your IBM Sales Representative.
Or don't use XA over client connections. |
Ok you'r right ! I surely miss somthing because it is the first time we use Client connection, because of a WLS cluster.
I have to see the all client installation process from the bigining !
Thanks for your "quick answer" !
_________________
MQSeries works on UNISYS OS2200 too !! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Feb 20, 2007 6:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You have to pay a license for the Extended Transactional Client!
Talk to your IBM Sales Representative.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Macjvi |
| Posted: Tue Feb 20, 2007 10:26 am Post subject: |
|
|
Newbie
Joined: 10 Jan 2006
Posts: 5
Location: Swizerland, Bern
|
So ... We do have a "site license" and the MQSeriesTXClient rpm is already installed....
It mean i do have the the Extended Transactional Client installed.....
It is not the problem.... Maybe it is a WLS configuration problem ? I keep looking for.....
_________________
MQSeries works on UNISYS OS2200 too !! |
|
| Back to top |
|
|
| sumantony@gmail.com |
| Posted: Tue Mar 13, 2007 3:33 pm Post subject: |
|
|
Newbie
Joined: 13 Mar 2007
Posts: 2
|
| How did you all resolve the issue ? Am having the same issue and would like to know how you all fixed it |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Mar 14, 2007 5:30 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
Which issue? The AT040010 FDC, or the heuristic condition, or the setmqcap problem on the TX Client side?  |
|
| Back to top |
|
|
|
|
