RMI CONNECTIONS LEFT IN AN OBJECT-WAIT STATE CAUSE THREADS TO INCREASE
Last updated on OCTOBER 13, 2017
Applies to:Oracle Containers for J2EE - Version 10.1.3.3.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.
Several EJB components are used to modularize application logic. These EJB components are deployed within their own EAR file on an oracle application server 10.1.3.4 and are accessed via JNDI through a Java InitialContext.
Once going live with the system, a sharp increase in the number of threads created by OC4J is noticed during the use of the application. This number seems to climb constantly during processing. After a lot of tracing, the cause was isolated as RMI Connections left in an object-wait state. Using a sample (blank) EJBs and a web client to call them, it was determined that every JNDI request for an EJB object created one of these RMI connection threads that are not closed and released back to the operating system.
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