Creating a ThreadGroup is one thing, getting rid of it is quite another - you have to call ThreadGroup.destroy() from outside the ThreadGroup after all the member threads have terminated. Otherwise you have a classloader leak: <https://developer.opencloud.com/devportal/display/ENGBLOG/2009/03/11/Avoid+ThreadGroup+in+Resource+Adaptors>
I would recommend against using ThreadGroup in an OSGi environment. As the blogpost points out, starting with SE5 you have Thread.setUncaughtExceptionHandler() available. _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
