My Oracle Support Banner

MANY BLOCKED THREADS WITH RMICLIENTCONNECTION ON ORACLE APPLICATION SERVER 10.1.3.4 (Doc ID 820585.1)

Last updated on JULY 20, 2018

Applies to:

Oracle Containers for J2EE - Version: 10.1.3.0.0 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Symptoms

On 10.1.3.4 in Production, during execution of application, many RMI deadlock / blocked threads occur.

ERROR

Thread dump 3/6 "pool-3-thread-41"
prio=10 tid=0x022ef7e8 nid=0x263 waiting for monitor entry
[0x8fb7c000..0x8fb7f9f0]
at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:244)
- waiting to lock <0xbe69c3a0> (a com.evermind.server.rmi.RMIClientConnection)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:228)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:302)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:56)


OC4J container needs to be restarted to restore application proper execution.

.

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

Platforms: 1-914CU;

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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