Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57648111B6 for ; Tue, 16 Sep 2014 14:54:34 +0000 (UTC) Received: (qmail 97315 invoked by uid 500); 16 Sep 2014 14:54:34 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 97259 invoked by uid 500); 16 Sep 2014 14:54:34 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 97249 invoked by uid 99); 16 Sep 2014 14:54:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 14:54:34 +0000 Date: Tue, 16 Sep 2014 14:54:34 +0000 (UTC) From: "Remko Popma (JIRA)" To: log4j-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (LOG4J2-830) failure to shutdown JVM when join called on AsyncAppender thread MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LOG4J2-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-830: ---------------------------------- Assignee: Remko Popma > 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 > Assignee: Remko Popma > Priority: Minor > Fix For: 2.1 > > Attachments: output.txt > > > I've configured my maven project to run my small java program as part of the build process like so: > {code} > ... > > clean install > > > maven-compiler-plugin > 2.3.2 > > 1.8 > 1.8 > > > > org.codehaus.mojo > exec-maven-plugin > 1.3.2 > > > install > > java > > > > ... > {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: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org