[
https://issues.apache.org/jira/browse/LOG4J2-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-830:
-------------------------------
Description:
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.
was:
I've configured my maven project to run my small java program as part of the
build process like so:
...
<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>
...
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.
Is your thread a daemon thread? The AsyncAppender thread will never exit (it
runs in an eternal loop), but is a daemon thread, so if there are no other
threads then the VM can exit.
If your thread is a non-daemon thread then joining the AsyncAppender thread
will cause it to also run forever. However, the VM cannot exit because there
are still non-daemon threads running.
> 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]
