[infinispan-issues] [JBoss JIRA] (ISPN-2567) ClassCastException from org.infinispan.query.impl.LifecycleManager.cacheStopping

[Adrian Nistor (JIRA)]

Adrian Nistor created ISPN-2567:
-----------------------------------

             Summary: ClassCastException from org.infinispan.query.impl.LifecycleManager.cacheStopping
                 Key: ISPN-2567
                 URL: https://issues.jboss.org/browse/ISPN-2567
             Project: Infinispan
          Issue Type: Bug
          Components: Querying
    Affects Versions: 5.2.0.Beta4
            Reporter: Adrian Nistor
            Assignee: Adrian Nistor
             Fix For: 5.2.0.CR1


The object obtained from registry cannot be cast to SearchFactoryIntegrator because it was already removed and replaced with the dummy LifecycleManager.REMOVED_REGISTRY_COMPONENT.


{noformat}
2012-11-29 00:33:53,094 WARN  [TestingUtil] (testng-CollectionsIndexingTest) Problems killing cache manager org.infinispan.manager.DefaultCacheManager at 7e515f40@Address:null
java.lang.ClassCastException: java.lang.Object cannot be cast to org.hibernate.search.spi.SearchFactoryIntegrator
	at org.infinispan.query.impl.LifecycleManager.cacheStopping(LifecycleManager.java:241)
	at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:221)
	at org.infinispan.CacheImpl.stop(CacheImpl.java:542)
	at org.infinispan.CacheImpl.stop(CacheImpl.java:537)
	at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:740)
	at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:645)
	at org.infinispan.test.SingleCacheManagerTest.teardown(SingleCacheManagerTest.java:60)
	at org.infinispan.test.SingleCacheManagerTest.destroyAfterClass(SingleCacheManagerTest.java:90)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	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.invokeConfigurations(Invoker.java:138)
	at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:225)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114)
	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$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
2012-11-29 00:33:53,105 ERROR [TestCacheManagerFactory] (testng-CollectionsIndexingTest) 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!! (testng-CollectionsIndexingTest) Exiting because CollectionsIndexingTest has NOT shut down all the cache managers it has started !!!!!!!
!!!!!! (testng-CollectionsIndexingTest) The still-running cacheManager was created here: org.infinispan.query.indexedembedded.CollectionsIndexingTest.createCacheManager(CollectionsIndexingTest.java:61) !!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[testng-SearchMappingTest] Test testWithoutSearchMapping(org.infinispan.query.programmaticmapping.SearchMappingTest) succeeded.
{noformat}

--
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