[
https://issues.jboss.org/browse/ISPN-2538?page=com.atlassian.jira.plugin....
]
Marko Lukša commented on ISPN-2538:
-----------------------------------
This is probably not only a Infinispan-query problem, but a more general one.
The bug happens when Capedwarf shuts down a cache at the same time as
{{EmbeddedCacheManager}} is shutting down the same cache. The fix is to synchronize on
the EmbeddedCacheManager instance whenever you are manually shutting down the cache.
Not sure whether Infinispan should handle this or not.
Endless loop in TreeMap.remove at shutdown of query-enabled cache
-----------------------------------------------------------------
Key: ISPN-2538
URL:
https://issues.jboss.org/browse/ISPN-2538
Project: Infinispan
Issue Type: Feature Request
Components: Querying
Affects Versions: 5.2.0.Beta4
Reporter: Marko Lukša
Assignee: Marko Lukša
{code}
"MSC service thread 1-6" prio=6 tid=0x000000000d5b9000 nid=0x10a0 runnable
[0x000000000e45e000]
java.lang.Thread.State: RUNNABLE
at java.util.TreeMap.fixAfterDeletion(TreeMap.java:2215)
at java.util.TreeMap.deleteEntry(TreeMap.java:2173)
at java.util.TreeMap.remove(TreeMap.java:600)
at
org.infinispan.query.impl.LifecycleManager.cacheStopped(LifecycleManager.java:181)
at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:227)
at org.infinispan.CacheImpl.stop(CacheImpl.java:540)
at org.infinispan.CacheImpl.stop(CacheImpl.java:535)
at org.infinispan.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:348)
at
org.jboss.as.capedwarf.services.CacheLifecycleService.stop(CacheLifecycleService.java:94)
at
org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911)
at
org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
{code}
--
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