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 D215F172DF for ; Sat, 25 Oct 2014 04:04:34 +0000 (UTC) Received: (qmail 21816 invoked by uid 500); 25 Oct 2014 04:04:34 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 21758 invoked by uid 500); 25 Oct 2014 04:04: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 21748 invoked by uid 99); 25 Oct 2014 04:04:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Oct 2014 04:04:34 +0000 Date: Sat, 25 Oct 2014 04:04:34 +0000 (UTC) From: "Daniel Widdis (JIRA)" To: log4j-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (LOG4J2-880) ConsoleAppender hangs when writing to System.out in a spawned JVM 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-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Widdis updated LOG4J2-880: --------------------------------- Priority: Minor (was: Major) > ConsoleAppender hangs when writing to System.out in a spawned JVM > ----------------------------------------------------------------- > > Key: LOG4J2-880 > URL: https://issues.apache.org/jira/browse/LOG4J2-880 > Project: Log4j 2 > Issue Type: Wish > Affects Versions: 2.0.2 > Reporter: Daniel Widdis > Priority: Minor > > I am using Log4J2 in an application using Java Parallel Processing Framework (www.jppf.org). One of the features of JPPF is node provisioning, in which a node process can spawn additional JVMs. However, since the spawned JVMs do not have a "console" the only way to access System.out is by redirecting it to a file, which is done automatically. > By default, the ConsoleAppender sets {{follow="false"}}. However, rather than exiting gracefully doing nothing, it locks an OutputStreamManger and never releases it. This causes the application to hang. > The problem is easily worked around by setting {{follow="true"}} on the appender. However, I propose that the default behavior for {{follow="false"}} when System.out is unavailable (as in a spawned JVM) should simply return without doing anything, rather than locking resources. > Relevant stack trace of the thread holding the lock is shown below. The {{writeBytes()}} method never returned. Other threads attempted to write but were blocked because of this lock. > "pool-5-thread-6" prio=6 tid=0x000000000c0c2000 nid=0x2ce4 runnable [0x000000000d9ae000] > java.lang.Thread.State: RUNNABLE > at java.io.FileOutputStream.writeBytes(Native Method) > at java.io.FileOutputStream.write(Unknown Source) > at java.io.BufferedOutputStream.write(Unknown Source) > - locked <0x00000000d0063960> (a java.io.BufferedOutputStream) > at java.io.PrintStream.write(Unknown Source) > - locked <0x00000000d0063940> (a java.io.PrintStream) > at org.apache.logging.log4j.core.appender.OutputStreamManager.write(OutputStreamManager.java:122) > - locked <0x00000000d00638e0> (a org.apache.logging.log4j.core.appender.OutputStreamManager) > at org.apache.logging.log4j.core.appender.OutputStreamManager.write(OutputStreamManager.java:136) > at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:106) > at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:97) > at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:428) > at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:407) > at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:410) > at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:365) > at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:112) > at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:1336) > at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1325) > at org.apache.logging.log4j.spi.AbstractLogger.warn(AbstractLogger.java:1738) -- 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