Many Blocked Threads with RMICclientConnection on Oracle Application Server
(Doc ID 820585.1)
Last updated on OCTOBER 21, 2024
Applies to:
Oracle Containers for J2EE - Version 10.1.3.0.0 and laterInformation 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-<no>-thread-41"
prio=10 tid=<TID> nid=<NID> 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)
prio=10 tid=<TID> nid=<NID> 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.
.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |