6:18 p.m.
Infinispan fails to shutdown gracefully
---------------------------------------
Key: ISPN-1444
URL: https://issues.jboss.org/browse/ISPN-1444
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.0.1.FINAL, 4.2.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
6:26 p.m.
[
https://issues.jboss.org/browse/ISPN-1444?page=com.atlassian.jira.plugin....
]
Luc Boudreau commented on ISPN-1444:
------------------------------------
The last thing we managed to do was to get at a point where the threads would periodically
spit out the following stack traces.
log4j:ERROR Error occured while converting date.
java.lang.NullPointerException
at java.lang.System.arraycopy(Native Method)
at java.lang.AbstractStringBuilder.getChars(AbstractStringBuilder.java:328)
at java.lang.StringBuffer.getChars(StringBuffer.java:201)
at org.apache.log4j.helpers.ISO8601DateFormat.format(ISO8601DateFormat.java:130)
at java.text.DateFormat.format(DateFormat.java:316)
at
org.apache.log4j.helpers.PatternParser$DatePatternConverter.convert(PatternParser.java:443)
at org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:65)
at org.apache.log4j.PatternLayout.format(PatternLayout.java:506)
at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:310)
at
org.apache.log4j.DailyRollingFileAppender.subAppend(DailyRollingFileAppender.java:369)
at org.apache.log4j.WriterAppender.append(WriterAppender.java:162)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
at
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
at org.apache.log4j.Category.callAppenders(Category.java:206)
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.log(Category.java:856)
at org.jgroups.logging.Log4JLogImpl.error(Log4JLogImpl.java:64)
at org.jgroups.protocols.Discovery$PingSenderTask$1.run(Discovery.java:535)
at org.jgroups.util.TimeScheduler2$RecurringTask.run(TimeScheduler2.java:592)
at org.jgroups.util.TimeScheduler2$MyTask.run(TimeScheduler2.java:524)
at org.jgroups.util.TimeScheduler2$Entry.execute(TimeScheduler2.java:429)
at org.jgroups.util.TimeScheduler2$1.run(TimeScheduler2.java:295)
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:619)
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
5:06 p.m.
[
https://issues.jboss.org/browse/ISPN-1444?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1444:
----------------------------------------
If you run within an app server or Tomcat, you should disable the shutdown hooks cos they
make no sense whatsoever in a managed environment. This is of course configurable, i.e.
http://docs.jboss.org/infinispan/5.1/apidocs/config.html#ce_global_shutdown - You need to
set it to DONT_REGISTER
The exception you show comes from JGroups, so I'd direct the issue to
https://issues.jboss.org/browse/JGRP
Also, multicast-receiver, unicast-receiver, OOB-* are JGroups' threads.
I've no idea who TransferQueueBuilder thread belongs to.
I'm closing the JIRA cos there's no indication of a bug in Infinispan.
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
5:06 p.m.
[
https://issues.jboss.org/browse/ISPN-1444?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1444:
----------------------------------------
Feel free to reopen if needed :)
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
5:06 p.m.
[
https://issues.jboss.org/browse/ISPN-1444?page=com.atlassian.jira.plugin....
]
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
4581
days inactive
4584
days old
infinispan-issues@lists.jboss.org
4 comments
4 participants
participants (4)
-
Galder Zamarreño (Commented) (JIRA) -
Galder Zamarreño (Resolved) (JIRA)
-
Luc Boudreau (Commented) (JIRA)
-
Luc Boudreau (Created) (JIRA)