JDK-4936203 : ORB threads should have their own unique threadgroup
  • Type: Bug
  • Component: other-libs
  • Sub-Component: corba:orb
  • Affected Version: 5.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_8
  • CPU: sparc
  • Submitted: 2003-10-10
  • Updated: 2004-03-15
  • Resolved: 2004-12-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 betaFixed
Related Reports
Relates :  
JDK-4916766 - CORBA COMM_FAILURE when destroy() takes too long and close() happens
Description
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
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: tiger-beta2 INTEGRATED IN: tiger-beta
14-06-2004
EVALUATION Seems like a good idea. Do we have resources? ###@###.### 2003-12-02
02-12-2003