Description of problem: I encountered this problem on all configurations (RHEL6, Solaris, Windows) and it effectively prevents us from running the testsuite during release testing. The exceptions can be seen at: https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-FUNC/job/edg-60-community-testsuite-windows/jdk=java16_default,label=dev99-W2k8r2-x86_64/31/console https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-FUNC/job/edg-60-community-testsuite-rhel/13/jdk=openjdk-local,label=RHEL6/console https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-FUNC/job/edg-60-community-testsuite-solaris/34/jdk=java16_default,label=sol11_x86/ AFAIK, it is not related to specific tests. I saw this exception happening with various tests. Typically the exception looks like this: 2012-03-26 01:33:57,661 ERROR [TestCacheManagerFactory] (testng-RemoteAsyncAPITest) !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!! (testng-RemoteAsyncAPITest) Exiting because client.hotrod.RemoteAsyncAPITest has NOT shut down all the cache managers it has started !!!!!!! !!!!!! (testng-RemoteAsyncAPITest) The still-running cacheManager was created here: org.infinispan.client.hotrod.RemoteAsyncAPITest.createCacheManager(RemoteAsyncAPITest.java:51) !!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tristan reports this was a test bed configuration error (memory limitation)