globalThreadGroup not destroyed creates a classloader memory leak ----------------------------------------------------------------- Key: JGRP-1410 URL: https://issues.jboss.org/browse/JGRP-1410 Project: JGroups Issue Type: Bug Affects Versions: 3.0.1 Environment: linux w/ java 1.6 Reporter: Jean-Philippe Gariepy Assignee: Bela Ban Fix For: 3.2.2, 3.3 When all channels are closed, the globalThreadGroup is not destroyed. For a normal (i.e. non-web) application, this is not a problem since the process will exit anyway. However, for a Java Enterprise web application, this causes a classloader memory leak since the ThreadGroup object has strong references to JGroups instances having strong references to their class object having strong reference to their class loader. Since the class loader is pointed by strong references, the it cannot be garbage collected and hence a leak is created each time the web application is stopped.