SUN ORB's cleanup() code cleaned up an IIOPConnection that was in use and that caused a COMM_FAILURE exception to be thrown out the Application level code.

Basically whenever the connection table size exceeds the HighWaterMark (Default value is 240), the connection table cleanup code kicks in and tries to clean up upto NumberToReclaim (Default value is 5) number of connections. While the code seems to be trying to be careful in not cleaning up in use (busy) connections, it seems to be falling short and seems to be 
cleaning up connections that seem to be in use for the purpose of making IDL calls.

We are experiencing a problem with the SUN ORB's connection table cleanup code With 
java version "1.4.2_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b06)
Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode
Posted Date : 2006-06-07 08:44:20.0

N/A

The cause of this problem is that the ConnectionCache does not propertly
manage and serialize access to the state of the Connection.  A fix is planned
for JDK 7.
Posted Date : 2006-08-15 17:01:48.0