WAS 5.1 and MQ6.0 - Websphere

This is a discussion on WAS 5.1 and MQ6.0 - Websphere ; Hi, We have an environment where in WAS 5.1 is integrated with MQ6.0. As part of this a webservice application soapgateway is used to trasnmit xml messages as part of the soap Post Request. In some instances we could find ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: WAS 5.1 and MQ6.0

  1. WAS 5.1 and MQ6.0

    Hi,



    We have an environment where in WAS 5.1 is integrated with MQ6.0. As part of this a webservice application soapgateway is used to trasnmit xml messages as part of the soap Post Request. In some instances we could find that issue seems to prop within WAS 5.1 during sending processing the post repsonse and sending an internal status(which is also getting generated) back to MQ queues. Below is a trace in the log file.



    May 08, 2008 01:53:37 PM com.aon.ade.soap.send.SOAPTransmitBean transmitAttempt

    INFO: SOAP transmit (UUID: 58ab71b4-153a-11dd-a69a-00c0f03d5b7c, TransmitID: 380329) HTTP Status 200) Elapsed Time: 108992

    May 08, 2008 01:53:37 PM com.aon.ade.soap.send.SOAPTransmitBean processBusinessMessage

    INFO: Message Sent OK: UUID 58ab71b4-153a-11dd-a69a-00c0f03d5b7c

    May 08, 2008 01:53:42 PM com.aon.ade.soap.send.SOAPTransmitBean sendMQStatus

    WARNING: Couldn't send Status Message! CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:

    org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: ; nested exception is:

    javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout vmcid: 0x0 minor code: 0 completed: No

    May 08, 2008 01:53:50 PM com.aon.ade.messaging.mdb.MessageRouterMDB setMessageDrivenContext

    INFO: Message Driven Bean Starting: MDB Config:application=ADESOAP;backoutQueue=java:comp/env/jms/BACKOUT.QUEUE;errorQu eue=java:comp/env/jms/ERROR.QUEUE

    May 08, 2008 01:53:50 PM com.aon.ade.messaging.reader.MessageHandlerDelegat e initHome

    INFO: Message Handler Local interface found:java:comp/env/ejb/local/MessageHandler

    08/05/08 13:55:57:448 BST 5367af EJSContainer d ObjectResolverreinvoke(com.aon.ade.soap.mqsender._EJSRemoteState lessADESOAPMQ Sender_e07e8b74_Tie, sendStatusMessage)

    08/05/08 13:55:57:450 BST mapMethodInfo(2,null)

    08/05/08 13:55:57:450 BST 5367af EJSContainer mapMethodInfo
    08/05/08 13:55:57:450 BST EJBpreInvoke(2:sendStatusMessage)

    08/05/08 13:55:57:451 BST 5367af WrapperManage d preInvoke : pinned = true

    com.aon.ade.soap.mqsender.EJSRemoteStatelessADESOA PMQSender_e07e8b74

    08/05/08 13:55:57:451 BST 5367af EJSContainer d Retrieving bean meta data for bean ADESOAP#ADESOAPMQSender.jar#ADESOAPMQSender

    08/05/08 13:55:57:451 BST 5367af ComponentMeta d begin context ADESOAP#ADESOAPMQSender.jar#ADESOAPMQSender

    08/05/08 13:55:57:451 BST preInvoke

    08/05/08 13:55:57:452 BST completeTxTimeout

    08/05/08 13:55:57:452 BST] 5367af TranManagerIm I WTRN0041I: Transaction 57415344:00000000000014a30000000102bb3445a56e0f7c9 8c709f41ccf47ec8e98ae88494544 49375052443032[ has been rolled back.

    08/05/08 13:55:58:708 BST 5367af TransactionCo completeTxTimeout throwing CSITransactionRolledBackException
    08/05/08 13:55:58:709 BST setUncheckedException in param:com.ibm.websphere.csi.CSITransactionRolledba ckException: Transaction rolled back; nested exception is:

    javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout

    08/05/08 13:55:58:709 BST 5367af ExceptionUtil E CNTR0019E: Non-application exception occurred while processing method "sendStatusMessage". Exception data: com.ibm.websphere.csi.CSITransactionRolledbackExce ption: Transaction rolled back; nested exception is:

    javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout

    at com.ibm.ejs.csi.TransactionControlImpl.completeTxT imeout(TransactionControlImpl .java:1380)

    at com.ibm.ejs.csi.TransactionControlImpl.preInvoke(T ransactionControlImpl.java:28 3)

    at com.ibm.ejs.container.EJSContainer.preInvoke_inter nal(EJSContainer.java:2763)
    at com.ibm.ejs.container.EJSContainer.preInvoke(EJSCo ntainer.java:2503)

    at com.ibm.ejs.container.EJSContainer.preInvoke(EJSCo ntainer.java:2488)

    at com.aon.ade.soap.mqsender.EJSRemoteStatelessADESOA PMQSender_e07e8b74.sendStatus Message(Unknown Source)

    at com.aon.ade.soap.mqsender._MessageEJBSender_Stub.s endStatusMessage(_MessageEJBS ender_Stub.java:356)

    at com.aon.ade.soap.send.SOAPTransmitBean.sendMQStatu s(SOAPTransmitBean.java:1779)

    at com.aon.ade.soap.send.SOAPTransmitBean.processBusi nessMessage(SOAPTransmitBean. java:631)

    at com.aon.ade.soap.send.SOAPTransmitBean.processMess age(SOAPTransmitBean.java:173 )

    at com.aon.ade.soap.send.EJSLocalStatelessSOAPTransmi t_c81f7f7a.processMessage(Unk nown Source)

    at com.aon.ade.messaging.reader.MessageHandlerDelegat e.processMessage(MessageHandl erDelegate.java:58)

    at com.aon.ade.messaging.mdb.MessageRouterMDB.onMessa ge(MessageRouterMDB.java:294)

    at com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnM essage.run(MDBWrapper.java:20 8)

    at com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java:56 )

    at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage( MDBWrapper.java:197)

    at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBW rapper.java:175)

    at com.ibm.mq.jms.MQSession.run(MQSession.java:1592)

    at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHan dle.java:924)

    at com.ibm.ejs.jms.listener.ServerSession.connectionC onsumerOnMessage(ServerSessio n.java:740)

    at com.ibm.ejs.jms.listener.ServerSession.onMessage(S erverSession.java:525)

    at com.ibm.ejs.jms.listener.ServerSession.dispatch(Se rverSession.java:492)

    at sun.reflect.GeneratedMethodAccessor16.invoke(Unkno wn Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.ja va:25)

    at java.lang.reflect.Method.invoke(Method.java:324)

    at com.ibm.ejs.jms.listener.ServerSessionDispatcher.d ispatch(ServerSessionDispatch er.java:37)

    at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrap per.java:91)

    at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrap per.java:127)

    at com.ibm.ejs.jms.listener.ServerSession.run(ServerS ession.java:373)

    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:912)

    Caused by: javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout

    at com.ibm.ws.Transaction.JTA.TranManagerImpl.complet eTxTimeout(TranManagerImpl.ja va:589)

    at com.ibm.ws.Transaction.JTA.TranManagerSet.complete TxTimeout(TranManagerSet.java :641)

    at com.ibm.ejs.csi.TransactionControlImpl.completeTxT imeout(TransactionControlImpl .java:1372)



    Could you please suggest me what this issue might be due to.

  2. Re: WAS 5.1 and MQ6.0

    r_suriga@yahoo.co.in wrote:
    > Hi,
    >
    >
    >
    > We have an environment where in WAS 5.1 is integrated with MQ6.0. As part of this a webservice application soapgateway is used to trasnmit xml messages as part of the soap Post Request. In some instances we could find that issue seems to prop within WAS 5.1 during sending processing the post repsonse and sending an internal status(which is also getting generated) back to MQ queues. Below is a trace in the log file.
    >
    >


    >
    > Could you please suggest me what this issue might be due to.


    "javax.transaction.TransactionRolledbackException: Transaction is ended
    due to timeout"

    seems pretty self-explanatory.

+ Reply to Thread