My Oracle Support Banner

JMS Messages Are In Receive Status In Topic But Can't Be Picked Up By JMS Proxy Service (Doc ID 2771869.1)

Last updated on APRIL 27, 2021

Applies to:

Oracle Service Bus - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.3.0 version, OSB Core Functionality

JMS Messages are in receive status in the topic but can't be picked up by JMS Proxy Service. This leads to a backlog of large amounts of messages. From thread dump found lots of threads hang at

'oracle.dms.context.internal.AbstractContextFamily.lockCtxMapForWrite'

[STUCK] ExecuteThread: '33' for queue: 'weblogic.kernel.Default
(self-tuning)'" #93 daemon prio=1 os_prio=0 tid=0x00002acbec4b8000 nid=0x4940
waiting on condition [0x00002acc11d1b000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000002c9000020> (a
java.util.concurrent.locks.ReentrantReadWriteLock$FairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(Ab
stractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQu
euedSynchronizer.java:870)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSy
nchronizer.java:1199)
at
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantRead
WriteLock.java:943)
at
oracle.dms.context.internal.AbstractContextFamily.lockCtxMapForWrite(AbstractC
ontextFamily.java:329)
at
oracle.dms.context.internal.wls2.WLS2ContextFamily.addContext(WLS2ContextFamil
y.java:86)
at
oracle.dms.context.internal.wls2.WLS2ContextManager.createContext(WLS2ContextM
anager.java:148)
at
oracle.dms.context.internal.wls2.WLS2ContextManager.getContext(WLS2ContextMana
ger.java:110)
at
oracle.dms.context.internal.wls2.WLS2ContextManager.getContext(WLS2ContextMana
ger.java:45)
at
oracle.dms.context.DMSContextManager.getContext(DMSContextManager.java:546)
at oracle.dms.context.ExecutionContext.get(ExecutionContext.java:168)
at
com.bea.wli.sb.service.instancetracking.TrackingContextManagerFactory$DefaultT
rackingContextManager.initialize(TrackingContextManagerFactory.java:88)
at
com.bea.wli.sb.transports.jms.JmsInboundMDB.initializeDMSContext(JmsInboundMDB
.java:163)
at
com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:127)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:438)
at
weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.j
ava:361)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:297)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:5104)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4775)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:4170)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:127)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5624)
at
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkMana
gerImpl.java:678)
at
weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocati
onContextManager.java:352)
at
weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocatio
nContextManager.java:337)
at
weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.
java:57)
at
weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at
weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkMana
gerImpl.java:652)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)

Locked ownable synchronizers:
- None

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.