[infinispan-issues] [JBoss JIRA] (ISPN-3784) Exiting because has NOT shut down all the cache managers it has started

[Vitalii Chepeliuk (JIRA)]

Vitalii Chepeliuk created ISPN-3784:
---------------------------------------

             Summary: Exiting because has NOT shut down all the cache managers it has started
                 Key: ISPN-3784
                 URL: https://issues.jboss.org/browse/ISPN-3784
             Project: Infinispan
          Issue Type: Bug
          Components: Core API
    Affects Versions: 6.0.0.Final
         Environment: All environmets
            Reporter: Vitalii Chepeliuk
            Assignee: Mircea Markus
            Priority: Blocker


When following tests are running 
RemoteStoreTest
RemoteStoreRawValuesTest
Adaptor52xCustomLoaderTest
Adaptor52xCustomStoreTest
JdbcStringTest
FileStoreTest
MixedStoreWithManagedConnectionTest
JdbcMixedStore2Test
Following exception is thrown
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!! (testng-MixedStoreWithManagedConnectionTest) Exiting because *Test has NOT shut down all the cache managers it has started !!!!!!!
!!!!!! (testng-MixedStoreWithManagedConnectionTest) See allocation stacktrace to find out where still-running cacheManager (org.infinispan.manager.DefaultCacheManager at 51696e47@Address:null) was created: !!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

java.lang.Throwable
	at org.infinispan.test.fwk.TestCacheManagerFactory.addThreadCacheManager(TestCacheManagerFactory.java:373)
	at org.infinispan.test.fwk.TestCacheManagerFactory.newDefaultCacheManager(TestCacheManagerFactory.java:356)
	at org.infinispan.test.fwk.TestCacheManagerFactory.newDefaultCacheManager(TestCacheManagerFactory.java:68)
	at org.infinispan.test.fwk.TestCacheManagerFactory.createCacheManager(TestCacheManagerFactory.java:185)
	at org.infinispan.test.fwk.TestCacheManagerFactory.createCacheManager(TestCacheManagerFactory.java:170)
	at org.infinispan.test.fwk.TestCacheManagerFactory.createCacheManager(TestCacheManagerFactory.java:174)
	at org.infinispan.marshall.TestObjectStreamMarshaller.<init>(TestObjectStreamMarshaller.java:34)
	at org.infinispan.persistence.BaseStoreTest.setUp(BaseStoreTest.java:68)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:653)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
	at org.testng.TestRunner.privateRun(TestRunner.java:767)
	at org.testng.TestRunner.run(TestRunner.java:617)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
	at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
	at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
	at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)

All of tests are superclasses of BaseStoreTest. Tests are passing well but when after all tests checkManagersClosed() from TestCacheManagerFactory is called there are some RUNNING cache managers and VM is stopped.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira