[ 
https://issues.apache.org/jira/browse/LOG4J2-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691227#comment-13691227
 ] 

Thomas Neidhart commented on LOG4J2-280:
----------------------------------------

Could you provide a stacktrace of the thread that hangs? Looking at the code of 
the async appender, there is no apparent call that may block apart from the 
queue (but this is handled via the shutdown method).

We could also issue a thread.interrupt() before the call to join, but I would 
still like to see the stacktrace first.
                
> AsynchAppender's AsynchThread blocks Tomcat shutdown
> ----------------------------------------------------
>
>                 Key: LOG4J2-280
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-280
>             Project: Log4j 2
>          Issue Type: Bug
>         Environment: Log4j 2.0 beta 4, Tomcat 6, Java 6 @ Mac OS X
>            Reporter: Matej Vitásek
>
> Since I added an AsynchAppender to my configuration (to send mails with 
> errors asynchronously), my Tomcat refuses to shut down nicely. It always 
> freezes on a line like this:
> ...
> Jun 11, 2013 6:57:04 PM org.apache.coyote.http11.Http11Protocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-8080
> Jun 11, 2013 6:57:04 PM org.apache.coyote.http11.Http11Protocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-8443
> At this point, there is a non-daemon thread called "Thread-2" that, if I 
> kill, Tomcat stops nicely.
> I have traced this issue to the AsynchThread in AsynchAppender, and if I stop 
> using it in my configuration, Tomcat stops nicely again.
> Could you tell me what additional information I may provide to help track 
> down this issue?

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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to