WebLogic time-out considerations for transacted sessions

When using WebLogic JMS as a messaging system to receive messages in transactional mode and no messages are received for a period of time equal to the WebLogic transaction time-out value (defaults to 3600 seconds), an error message appears in the integration server.

After the following error message appears, no messages can be processed and you must relaunch the adapter in order to process any messages that recently arrived.

<date-time> [Thread-6] ERROR services.jms.JMSConsumer  -Could not successfully 
process message
weblogic.jms.common.TransactionRolledBackException:
        at weblogic.rmi.internal.BasicOutboundRequest.sendReceive
        (BasicOutboundRequest.java:85)
        at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:135)
        at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
        at $Proxy2.dispatchSyncNoTranFuture(Unknown Source)
        at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran
        (DispatcherWrapperState.java:341)
        at weblogic.jms.client.JMSSession.receiveMessage(JMSSession.java:347)
        at weblogic.jms.client.JMSConsumer.receive(JMSConsumer.java:333)
        at weblogic.jms.client.JMSConsumer.receive(JMSConsumer.java:279)
        at com.yantra.interop.services.jms.JMSConsumer.run(JMSConsumer.java:204)
        at java.lang.Thread.run(Thread.java:512)

For help with choosing an appropriate transaction time-out value for your system, see your WebLogic documentation.