-
Bug
-
Resolution: Won't Fix
-
P3
-
1.4.2_11
-
x86
-
windows_xp
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2164513 | 6-pool | Sunita Koppar | P3 | Closed | Won't Fix | |
JDK-2164512 | 5.0-pool | Sunita Koppar | P3 | Closed | Won't Fix | |
JDK-2168769 | 1.4.2_19 | Abhijit Saha | P3 | Resolved | Fixed | b01 |
JDK-2154604 | 1.4.2_18-rev | Mike Belopuhov | P2 | Resolved | Fixed | b08 |
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
- backported by
-
JDK-2154604 SUN ORB's connection table cleanup code cleans up "in use"
-
- Resolved
-
-
JDK-2168769 SUN ORB's connection table cleanup code cleans up "in use"
-
- Resolved
-
-
JDK-2164512 SUN ORB's connection table cleanup code cleans up "in use"
-
- Closed
-
-
JDK-2164513 SUN ORB's connection table cleanup code cleans up "in use"
-
- Closed
-
- relates to
-
JDK-6929137 java-corba: Locking too broad in com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl
-
- Closed
-
-
JDK-6637818 NIGHTLY: Two JCK tests throw NPE due to changes in com.sun.corba.se.internal.corba.ClientDelegate.ja
-
- Closed
-