My Oracle Support Banner

Deadlock In OC4J While Lookup JNDI Resources (Doc ID 781549.1)

Last updated on OCTOBER 19, 2018

Applies to:

Oracle Containers for J2EE - Version: to - Release: AS10g to AS10gR2
Oracle Solaris on SPARC (32-bit)
Sun Solaris SPARC (32-bit)


On OC4J - :

When running JNDI lookup in J2EE application deployed on OC4J , the lookup intermittantly hangs. Bouncing the server and restarting it usually fixes the problem.

Found three Java-level deadlocks
waiting to lock monitor 0xd9c08 (object 0xb638e238, a java.util.HashMap),
which is held by "ApplicationServerThread-13"
waiting to lock monitor 0x6070c8 (object 0xb6310190, a com.evermind.server.rmi.RMIServer),
which is held by "RMIConnectionThread"

Java stack information for the threads listed above

at com.evermind.server.rmi.RMIContext.unbindAll(
- waiting to lock <b638e238> (a java.util.HashMap)
at com.evermind.server.rmi.RMIServer.unbindAll(
- locked <b6310190> (a com.evermind.server.rmi.RMIServer)
at com.evermind.server.rmi.RMIConnection.disconnect(
at com.evermind.server.rmi.RMIServer.getContext(
- waiting to lock <b6310190> (a com.evermind.server.rmi.RMIServer)
at com.evermind.server.rmi.RMIContext.lookupLocalObject(
- locked <b638e238> (a java.util.HashMap)
at com.evermind.server.rmi.RMIContext.lookup(
at com.evermind.server.ApplicationContext.lookup(
at com.evermind.server.ApplicationContext.lookup(
at javax.naming.InitialContext.lookup(


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

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.