Consumer creation failed due to existence in indoubt txn list

(Doc ID 1279590.1)

Last updated on OCTOBER 16, 2017

Applies to:

Oracle Retail Integration Bus - Version: 5.0.5 and later   [Release: 5 and later ]
Information in this document applies to any platform.

Symptoms

Error in the server.log:

|WARNING|sun-appserver2.1|com.stc.jmsjca.core.Activation|_ThreadID=95;_ThreadName=JMSJCA connect;Context=prjJC_RIC_KGH_ADT/svcID_RIC_KGH_ADT/etUltiCareADT2_5IN;_RequestID=e38a82d1-884c-4ae5-b671-7a2fbbf7342f;|JMSJCA-E016: [sync-Durable TopicSubscriber(prjJC_RIC_KGH_ADT_etUltiCareADT2_5_svcID_RIC_KGH_ADT)(etUltiCareADT2_5){prjJC_RIC_KGH_ADT/svcID_RIC_KGH_ADT/etUltiCareADT2_5IN} @ [stcms453://ks08p01:28007]]: message delivery initiation failed (attempt #153); will retry in 10 seconds. The error was: Consumer creation failed due to existence in indoubt txn list
com.stc.jmsjca.util.Exc$ConsumerCreationException: Consumer creation failed due to existence in indoubt txn list
at com.stc.jmsjca.core.RAJMSObjectFactory.createMessageConsumer(RAJMSObjectFactory.java:547)
at com.stc.jmsjca.core.SyncDelivery$SyncWorker.init(SyncDelivery.java:504)
at com.stc.jmsjca.core.SyncDelivery.start(SyncDelivery.java:202)
at com.stc.jmsjca.core.Activation.asyncStart(Activation.java:552)
at com.stc.jmsjca.core.Activation.access$000(Activation.java:81)
at com.stc.jmsjca.core.Activation$1.run(Activation.java:347)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.jms.JMSException: Consumer creation failed due to existence in indoubt txn list
at com.seebeyond.jms.sockets.ConsumerSocket.<init>(ConsumerSocket.java:114)
at com.seebeyond.jms.sockets.SessionSocket.createConsumerSocket(SessionSocket.java:101)
at com.seebeyond.jms.sockets.SocketProtocolMgr.registerConsumer(SocketProtocolMgr.java:145)
at com.seebeyond.jms.client.STCSession.registerMessageConsumer(STCSession.java:859)
at com.seebeyond.jms.client.STCTopicSubscriber.<init>(STCTopicSubscriber.java:61)
at com.seebeyond.jms.client.STCTopicSession.createDurableSub

Changes

On a production, the server ran out of PermGen space,  user killed -9 to stop and restarted the domain.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms