ORMI Over HTTP Tunnelling: Performance Considerations
Last updated on SEPTEMBER 15, 2017
Applies to:Oracle Containers for J2EE - Version: 10.1.3.0.0 to 220.127.116.11.0 - Release: AS10gR3 to FMw 11g
Information in this document applies to any platform.
You are executing a servlet/JSP RMI application within OC4J 10.1.3.0.0 or higher, under load conditions. The application will invoke an ORMI call at a remote OC4J using ORMI over HTTP tunneling.
You notice extremely slow response times, for example in one support test case, with 100 users, a response time of 100 seconds or more is observed. A thread dump is taken and it shows only one AJPRequestHandler-RMICallHandler is in a runnable state while all others are in blocked state.
Thread Dump Stack Trace))
Monitor:Waiting for Monitor Lock on
at com/evermind/server/rmi/RMIClientConnection.invokeMethod(RMIClientConnection.java:474(Compiled Code
What is the reason for the threads being blocked in a wait state ?
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