Deadlock In JMQ Query Causing Message Backlogs

(Doc ID 1377576.1)

Last updated on AUGUST 28, 2017

Applies to:

Oracle Java CAPS - Version 5.1.3 and later
Information in this document applies to any platform.
Checked for relevance on 30-DEC-2011
***Checked for relevance on 02-October-2014***

Symptoms


Production stopped processing messages, the Oracle RAC database reported deadlocks and the following errors were seen in Java CAPS:

[#|2011-10-06T03:47:01.945-0700|SEVERE|sun-appserver2.1.1|javax.enterprise.system.container.ejb|_ThreadID=1415;_ThreadName=JMSJCA sync #0(tCVR.ip.EPICad.in);Context=MM_EPICadAMCOM_ip/svcMM_EPICadAMCOM_ip/tCVR.ip.EPICad.inIN;_RequestID=255de8b0-3f6e-4522-9e41-40de2e8833ee;|com.stc.codegen.OTDImpl.runtime.ejb.OTDService: Cannot load from BACKUPSTORE FOR Key: <98900a21009b1f-ffffffffc21c4115-8c29>|#]

[#|2011-10-06T03:47:01.968-0700|SEVERE|sun-appserver2.1.1|MM_EPICadAMCOM_ip.svcMM_EPICadAMCOM_ip.jcdMM_EPICadAMCOM_ip_Runtime_Handler|_ThreadID=1415;_ThreadName=JMSJCA sync #0(tCVR.ip.EPICad.in);Context=MM_EPICadAMCOM_ip/svcMM_EPICadAMCOM_ip/tCVR.ip.EPICad.inIN;_RequestID=255de8b0-3f6e-4522-9e41-40de2e8833ee;|javax.ejb.NoSuchObjectLocalException: The EJB does not exist. session-key: 98900a21009b1f-ffffffffc21c4115-8c29
javax.ejb.NoSuchObjectLocalException: The EJB does not exist. session-key: 98900a21009b1f-ffffffffc21c4115-8c29
at com.sun.ejb.containers.StatefulSessionContainer._getContext(StatefulSessionContainer.java:1220)
at com.sun.ejb.containers.BaseContainer.getContext(BaseContainer.java:1731)
at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:1260)

[#|2011-10-06T03:49:51.139-0700|INFO|sun-appserver2.1.1|MM_EPICadAMCOM_ip.svcMM_EPICadAMCOM_ip.jcdMM_EPICadAMCOM_ip_Runtime_Handler|_ThreadID=1415;_ThreadName=JMSJCA sync #0(tCVR.ip.EPICad.in);Context=MM_EPICadAMCOM_ip/svcMM_EPICadAMCOM_ip/tCVR.ip.EPICad.inIN;|----- Transaction will be rolled back--------|#]

[#|2011-10-06T03:50:04.936-0700|WARNING|sun-appserver2.1.1|com.stc.jmsjca.core.Delivery|_ThreadID=1415;_ThreadName=JMSJCA sync #0(tCVR.ip.EPICad.in);Context=MM_EPICadAMCOM_ip/svcMM_EPICadAMCOM_ip/tCVR.ip.EPICad.inIN;_RequestID=7d6ac309-5b50-4abc-9046-90a5810c42a4;|JMSJCA-E031: The entity the message was sent to for processing, threw an exception. The message will be rolled back. Exception: [message-driven bean method public abstract void javax.jms.MessageListener.onMessage(javax.jms.Message) system exception]
javax.ejb.EJBException: message-driven bean method public abstract void javax.jms.MessageListener.onMessage(javax.jms.Message) system exception
at com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:1146)
at com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:74)
at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:179)
at $Proxy645.onMessage(Unknown Source)

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