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

Remko Popma commented on LOG4J2-830:
------------------------------------

Ah, good!

As for the improvement that Log4j can make: currently in the main while loop in 
the AsyncAppender thread, InterruptedExceptions are caught and ignored. It 
looks like Maven(or Mojo?) tried to interrupt the thread but this was ignored. 

(from output.txt)
{code}
[WARNING] thread Thread[AsyncAppender-fileAsync,5,...] was interrupted but is 
still alive after waiting at least 15000msecs
[WARNING] thread Thread[AsyncAppender-fileAsync,5,...] will linger despite 
being asked to die via interruption
{code}

It may be better to break out of the while loop when interrupted and execute 
the shutdown logic that immediately follows.

> failure to shutdown JVM when join called on AsyncAppender thread
> ----------------------------------------------------------------
>
>                 Key: LOG4J2-830
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-830
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.0.2
>         Environment: Windows 7
> Java 8 update 20 64 & 32 bit
>            Reporter: Adam Honen
>            Priority: Minor
>         Attachments: output.txt
>
>
> I've configured my maven project to run my small java program as part of the 
> build process like so:
> {code}
> ...
>   <build>
>     <defaultGoal>clean install</defaultGoal>
>     <plugins>
>       <plugin>
>         <artifactId>maven-compiler-plugin</artifactId>
>         <version>2.3.2</version>
>         <configuration>
>           <source>1.8</source>
>           <target>1.8</target>
>         </configuration>
>       </plugin>
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>exec-maven-plugin</artifactId>
>         <version>1.3.2</version>
>         <executions>
>           <execution>
>             <phase>install</phase>
>             <goals>
>               <goal>java</goal>
>             </goals>
>           </execution>
>         </executions>
> ...
> {code}
> After adding log4j 2.0.2 maven started experiencing issues completing the 
> build process. Luckily it has a timeout, so the only effect is a slow down of 
> the build process, while everything else still works.
> Also the program itself, when run outside maven, finishes without issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to