|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQ Compatibility Issue with WebLogic |
« View previous topic :: View next topic » |
Author |
Message
|
bearsonli |
Posted: Tue Jul 25, 2006 7:00 am Post subject: MQ Compatibility Issue with WebLogic |
|
|
Novice
Joined: 02 Mar 2004 Posts: 16
|
I have a MQ5.3 CSD07 and WebLogic 8.1 SP4 architecture, with WebLogic's MDB polling msgs from MQ queue. I am using a startup class that connects to MQ in binding mode rather than using messaging bridge.
I recently upgraded MQ to CSD12 and started seeing XA related errors below. I then upgraded WLS to SP5 which contains the CR211194 as mentioned in the system requirement of MQ in:
http://www-1.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&context=SSWHKB&q1=MQ+system+requirement&q2=5.3&q3=Solaris&uid=swg27006275&loc=en_US&cs=utf-8&lang=en
However the XA errors persisted.
Has anybody experienced the same problem? I have also contacted IBM for this but would like to share with you guys.
Sincerely.
Li
####<Jul 24, 2006 7:43:23 PM CDT> <Error> <JTA> <acthsnte1> <Ths1> <ExecuteThread: '0' for queue: 'weblogic.ejb20.internal.JMSMessagePoller'> <<anonymous>> <BEA1-0004012117D3A8C65565> <BEA-110412> <Name=JMSMessagePoller.tdiMDB,Xid=BEA1-0004012117D3A8C65565(759461),Status=Rolled back. [Reason=Unknown],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds left=59970,activeThread=Thread[ExecuteThread: '0' for queue: 'weblogic.ejb20.internal.JMSMessagePoller',5,Thread Group for Queue: 'weblogic.ejb20.internal.JMSMessagePoller'],XAServerResourceInfo[weblogic.ejb20.JMSConnectionPoller.tdiMDB]=(ServerResourceInfo[weblogic.ejb20.JMSConnectionPoller.tdiMDB]=(state=rolledback,assigned=Ths1),xar=weblogic.deployment.jms.WrappedXAResource_com_ibm_mq_MQXAResource@cf2fc9,re-Registered = false),SCInfo[THS+Ths1]=(state=rolledback),properties=({weblogic.transaction.name=JMSMessagePoller.tdiMDB}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=Ths1+acthsnte1.cbot.com:6050+THS+t3+, XAResources={},NonXAResources={})],CoordinatorURL=Ths1+acthsnte1.cbot.com:6050+THS+t3+) completed heuristically: (weblogic.ejb20.JMSConnectionPoller.tdiMDB, HeuristicHazard, (javax.transaction.xa.XAException: XA operation failed, see errorCode)) >
####<Jul 24, 2006 7:43:23 PM CDT> <Error> <EJB> <acthsnte1> <Ths1> <ExecuteThread: '0' for queue: 'weblogic.ejb20.internal.JMSMessagePoller'> <<anonymous>> <> <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.tdiMDB, HeuristicHazard, (javax.transaction.xa.XAException: XA operation failed, see errorCode))
The exception is : javax.transaction.SystemException: Heuristic hazard: (weblogic.ejb20.JMSConnectionPoller.tdiMDB, HeuristicHazard, (javax.transaction.xa.XAException: XA operation failed, see errorCode))
at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:386)
at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:352)
at weblogic.ejb20.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:305)
at weblogic.ejb20.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:334)
at weblogic.ejb20.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:450)
at weblogic.ejb20.internal.JMSMessagePoller.execute(JMSMessagePoller.java:466)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
> |
|
Back to top |
|
 |
mvic |
Posted: Tue Jul 25, 2006 7:30 am Post subject: Re: MQ Compatibility Issue with WebLogic |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
bearsonli wrote: |
Has anybody experienced the same problem? I have also contacted IBM for this but would like to share with you guys. |
Probably wise to call BEA as well; I searched for "mq" through the exception information below, but found nothing that looks like it has originated from MQ's Java or JMS classes. |
|
Back to top |
|
 |
bearsonli |
Posted: Tue Jul 25, 2006 8:09 am Post subject: |
|
|
Novice
Joined: 02 Mar 2004 Posts: 16
|
Did contact BEA. However the support technician assigned to this case had no clue (my typical BEA experience while dealing with MQ related issues) and asked for all the deployment descriptor file etc.
I am surprised that this is NOT a common problem between MQ and WebLogic.
I suspect that this is a "communication" problem b/t the XA resource managers of MQ and WLS. Also, I forgot to mention that these XA errors were only generated when there's no msg in the q. I know the MDB works by listening on the q (forever), and the XA time out at WLS is set to 30 seconds. That means when the q has been empty for longer than 30 sec, WLS decides to rollback the txn. All above is expected behavior but what I don't understand is why all of a sudden WLS starts logging such errors after MQ5.3 is upgraded to CSD12. |
|
Back to top |
|
 |
Nigelg |
Posted: Wed Jul 26, 2006 6:37 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
The probable reason is that Weblogic has a protocol error which was tolerated by WMQ at earlier CSDs, and which is not more strictly enforced at CSD12.
Contact IBM support in the first instance, but if the above is the reason then the fix has to come from Weblogic. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
iperel |
Posted: Tue Oct 03, 2006 12:49 pm Post subject: Weblogic Patch to resolve WL 8.1 SP4 and MQ 5.3 CSD12 issue |
|
|
Newbie
Joined: 05 Aug 2004 Posts: 7 Location: Kansas City
|
Weblogic has a patch available for this issue
CR269661_81sp4 |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|