This discussion is archived
7 Replies Latest reply: Sep 5, 2012 10:30 PM by 462890 RSS

MQ client upgrade to V7 on weblogic server

Redbox009 Newbie
Currently Being Moderated
After upgrading Websphere MQ client from V6 to V7 on weblogic server seeing below errors in the application logs


####<Jul 23, 2012 9:31:48 AM CDT> <Warning> <JTA> <mn4s34003> <d1_managed1> <[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1343053908099> <BEA-110484> <The JTA health state has changed from HEALTH_OK to HEALTH_WARN with reason codes: Resource weblogic.deployment.jms.WrappedXAResource_com_ibm_mq_jmqi_JmqiXAResource declared unhealthy.>
####<Jul 23, 2012 9:31:48 AM CDT> <Warning> <JTA> <mn4s34003> <d1_managed1> <[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1343053908099> <BEA-110204> <XA resource [weblogic.deployment.jms.WrappedXAResource_com_ibm_mq_jmqi_JmqiXAResource] returns XAER_RMFAIL and is unavailable.>


weblogic.transaction.RollbackException: delist() failed on resource 'weblogic.deployment.jms.WrappedXAResource_com_ibm_mq_jmqi_JmqiXAResource'.
The method 'xa_end' has failed with errorCode '100'.
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1881)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:345)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:553)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:424)
at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:234)
at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:105)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: javax.transaction.xa.XAException: The method 'xa_end' has failed with errorCode '100'.

has anyone faced any similar kind of issues while upgrading MQ client? any ideas how to fix this?
  • 1. Re: MQ client upgrade to V7 on weblogic server
    Kalyan Pasupuleti-Oracle Expert
    Currently Being Moderated
    Hi,

    by looking @

    reason codes: Resource weblogic.deployment.jms.WrappedXAResource_com_ibm_mq_jmqi_JmqiXAResource declared unhealthy

    it seems that your JMS Adapter is available or inactive mode while doing transaction.

    Try to untraget and trarget it again it should work.

    Please raise a ticket with Oracle support ticket also that will help you to get more near to root cause....

    Regards,
    Kal
  • 2. Re: MQ client upgrade to V7 on weblogic server
    Redbox009 Newbie
    Currently Being Moderated
    Thanks for your reply.

    we are using Foreign JMS provider instead of MQ adapter. All the required MQ client jars are placed under the <domain>/lib.

    Thanks
  • 3. Re: MQ client upgrade to V7 on weblogic server
    Tom B Expert
    Currently Being Moderated
    I googled The method 'xa_end' has failed with errorCode '100'., which yielded this from IBM:
    http://www-01.ibm.com/support/docview.wss?uid=swg21508472

    The cause of these errors is usually the result of a WebSphere MQ messaging provider JMS Connection being closed off by WebSphere Application Server because the Aged timeout for the Connection has expired.

    To resolve this issue, ensure that the JMS Connection Factory being used by the application has the Connection Pool property Aged timeout set to zero. This will prevent JMS Connections being closed when they are returned to the Free Pool, and so ensures that any outstanding transactional work can be completed.
    I realize this advice is meant to apply to WAS, but perhaps MQ is running the same type of connection pool implicitly on WL.
  • 4. Re: MQ client upgrade to V7 on weblogic server
    Redbox009 Newbie
    Currently Being Moderated
    Thanks for looking into this Tom.

    I did check with IBM support if there is any "Aged Time Out" setting on the connection factory or on the MQ end that I could change but they mentioned it is the setting that need to be made on the Weblogic end. Do you know anything about this setting on weblogic server?

    Thanks
  • 5. Re: MQ client upgrade to V7 on weblogic server
    Tom B Expert
    Currently Being Moderated
    There is no way for WebLogic to configure specific proprietary attributes such as "Aged Time Out" on a foreign vendor's connection factory as this is not covered by the JMS or Java EE specifications. WebLogic simply uses an existing IBM connection factory that it has been told to find by looking it up in the foreign provider's JNDI.

    In other words, a WebLogic administrator/developer only configures the URL of the foreign provider's JNDI implementation and the CF name for the JNDI location of a foreign provider's CF. Typically this configuration is accomplished using WebLogic's Foreign JMS Server feature, which essentially maps remote JNDI entries into local JNDI. The foreign JNDI and CF are themselves configured by the foreign provider's tooling.

    Tom
  • 6. Re: MQ client upgrade to V7 on weblogic server
    Redbox009 Newbie
    Currently Being Moderated
    Thanks Tom for your reply.

    Any other thoughts on this issue?
  • 7. Re: MQ client upgrade to V7 on weblogic server
    462890 Newbie
    Currently Being Moderated
    Is the MQ queue being used in this transaction a local queue on the same queue manager where client connects or some kind or clustered queue or remote queue for which the consumer may be on a different queue manager?

    I don't have a solution here but we have a similar problem where we may receive messages on different servers and may route it to a single consumer on some other box reading on a queue. each box has its own queue manager so the consumer's queue is clustered for all producers to put messages on it.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points