[infinispan-issues] [JBoss JIRA] (ISPN-1444) Infinispan fails to shutdown gracefully
Galder Zamarreño (Resolved) (JIRA)
jira-events at lists.jboss.org
Mon Oct 10 11:06:19 EDT 2011
[ https://issues.jboss.org/browse/ISPN-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Galder Zamarreño resolved ISPN-1444.
------------------------------------
Resolution: Rejected
> Infinispan fails to shutdown gracefully
> ---------------------------------------
>
> Key: ISPN-1444
> URL: https://issues.jboss.org/browse/ISPN-1444
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 4.2.1.FINAL, 5.0.1.FINAL
> Reporter: Luc Boudreau
> Assignee: Manik Surtani
> Priority: Blocker
>
> We have embeded Infinispan into our project, but when used, we cannot gracefully shutdown the JVM anymore.
> There are a few exceptions thrown by late-access to the classloader from log4j, but these errors are easy to work around. Tomcat blocks any class loading after an application has been marked as shutting down. I can load them in the classloader in my application at runtime and circumvent those issues.
> The main problem is the fact that the threads are just hanging there. They are not marked as daemon threads, so the JVM doesn't shut them off automatically, if required. The culprit threads are:
> - OOB-1
> - OOB-2
> - multicast receiver
> - unicast-receiver
> - TransferQueueBuilder
> Some of these threads might be related to JGroups. Please advise, and I will create a separate ticket in their bug tracker if needed.
> I know Infinispan registers a shutdown hook in order to cleanly shut down, but it looks quite unreliable and causes a lot of problems for us.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list