WebLogic 10.3.3 - Deadlock between "weblogic.jms.frontend.FESession" And "weblogic.jms.frontend.FEConnection" (Doc ID 1289117.1)

Last updated on AUGUST 03, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.3 and later
Information in this document applies to any platform.

Symptoms

In a WebLogic 10.3.3 Server Domain that contains two managed servers in cluster which are used exclusively as a JMS server and no application is deployed in these managed servers. Sometimes these servers (one or both) are in state FAILED. Below is STUCK thread trace at the time of the issue.

"[STUCK] ExecuteThread: '67' for queue: 'weblogic.kernel.Default (self-tuning)'":
at weblogic.jms.frontend.FEConnection.stop(FEConnection.java:671)
- waiting to lock <643c4708> (a weblogic.jms.frontend.FESession)
- locked <615dbe70> (a weblogic.jms.frontend.FEConnection)
at weblogic.jms.frontend.FEConnection.close(FEConnection.java:456)
- locked <615dbe70> (a weblogic.jms.frontend.FEConnection)
at weblogic.jms.frontend.FEConnection.dispatcherPeerGone(FEConnection.java:1301)
at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:692)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

"[ACTIVE] ExecuteThread: '60' for queue: 'weblogic.kernel.Default (self-tuning)'":
at weblogic.jms.frontend.FEConnection.getPeerVersion(FEConnection.java:1381)
- waiting to lock <615dbe70> (a weblogic.jms.frontend.FEConnection)
at weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:784)
- locked <643c4708> (a weblogic.jms.frontend.FESession)
at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1025)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2995)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)



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