-
Bug
-
Resolution: Fixed
-
P3
-
5.0
-
beta
-
sparc
-
solaris_8
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2075816 | 5.0 | Ken Cavanaugh | P3 | Closed | Fixed | beta2 |
All of the ORB threads should have their own unique threadgroup.
We should give the ThreadGroup a unique, ORB specific name (something like "ORB." +
System.identityHashCode( this ) inside the ORB constructor), and then make sure that properly shutting
down the ORB also destroys the ThreadGroup after first shutting down all of the threads.
For related info. please also see bug 4916766
###@###.### 2003-10-10
###@###.### 2004-03-15
We should give the ThreadGroup a unique, ORB specific name (something like "ORB." +
System.identityHashCode( this ) inside the ORB constructor), and then make sure that properly shutting
down the ORB also destroys the ThreadGroup after first shutting down all of the threads.
For related info. please also see bug 4916766
###@###.### 2003-10-10
###@###.### 2004-03-15
- backported by
-
JDK-2075816 ORB threads should have their own unique threadgroup
-
- Closed
-
- relates to
-
JDK-4916766 CORBA COMM_FAILURE when destroy() takes too long and close() happens
-
- Resolved
-