Jenkins build is unstable: Log4j 2.x #1854

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Comment Edited] (LOG4J2-1343) Update ConsoleAppender to utilize gc-free Layout method

[ https://issues.apache.org/jira/browse/LOG4J2-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231625#comment-15231625 ] Remko Popma edited comment on LOG4J2-1343 at 4/8/16 4:50 AM: - The current

[jira] [Reopened] (LOG4J2-1343) Update ConsoleAppender to utilize gc-free Layout method

[ https://issues.apache.org/jira/browse/LOG4J2-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1343: - The current implementation that coarsely locks on the Appender Manager causes a deadlock in

[jira] [Commented] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231614#comment-15231614 ] Matt Sicker commented on LOG4J2-1359: - If there's no way to mix the compile environment, then I guess

[jira] [Created] (LOG4J2-1360) Add bridge to JDK9 System.Logger interface

Matt Sicker created LOG4J2-1360: --- Summary: Add bridge to JDK9 System.Logger interface Key: LOG4J2-1360 URL: https://issues.apache.org/jira/browse/LOG4J2-1360 Project: Log4j 2 Issue Type: New

[jira] [Updated] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1359: Labels: jdk9 (was: ) > Add support for Java 9 StackWalker API in ReflectionUtil >

[jira] [Commented] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231610#comment-15231610 ] Remko Popma commented on LOG4J2-1359: - Interesting. Given the need to compile this with javac 1.9,

[jira] [Commented] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231611#comment-15231611 ] Ralph Goers commented on LOG4J2-1359: - I tested StackWalker a few weeks ago. I don't remember the

[jira] [Updated] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1359: Description: [StackWalker|http://download.java.net/jdk9/docs/api/java/lang/StackWalker.html]

[jira] [Created] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

Matt Sicker created LOG4J2-1359: --- Summary: Add support for Java 9 StackWalker API in ReflectionUtil Key: LOG4J2-1359 URL: https://issues.apache.org/jira/browse/LOG4J2-1359 Project: Log4j 2

Re: Build failed in Jenkins: Log4j 2.x #1852

I'm assuming this is caused by one on my recent changes. The reasons I can think of is either the change to SimpleMessage to carry a CharSequence, or the wider lock in the file/console appenders: in the gc-free mechanism the Layout converts a LogEvent to bytes within a synchronized block.

Re: Build failed in Jenkins: Log4j 2.x #1852

> Build timed out (after 240 minutes). Marking the build as failed. Whoa. On 7 April 2016 at 15:40, Apache Jenkins Server wrote: > See > > Changes: > > [rpopma] LOG4J2-1326 modify SimpleMessage and

Build failed in Jenkins: Log4j 2.x #1852

See Changes: [rpopma] LOG4J2-1326 modify SimpleMessage and ReusableSimpleMessage so they can [rpopma] LOG4J2-1326 ReusableSimpleMessage test fix [rpopma] LOG4J2-1326 add methods to Logger interface that explicitly accept a [rpopma]

[jira] [Comment Edited] (LOG4J2-1326) API change: add methods for logging CharSequences (was: Provide support for CharSequence parameters for low and zero-GC applications)

[ https://issues.apache.org/jira/browse/LOG4J2-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230437#comment-15230437 ] Remko Popma edited comment on LOG4J2-1326 at 4/7/16 3:45 PM: - Fixed in

[jira] [Resolved] (LOG4J2-1326) API change: add methods for logging CharSequences (was: Provide support for CharSequence parameters for low and zero-GC applications)

[ https://issues.apache.org/jira/browse/LOG4J2-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1326. - Resolution: Fixed Fixed in master. Adding these methods to the Logger interface: {code}

Re: Markers Markers

They should be. You can always create a marker that acts as a collection of other markers, so there is no need to support a list in the LogEvent. Ralph > On Apr 7, 2016, at 7:03 AM, Matt Sicker wrote: > > Aren't hierarchical markers good enough for that? > > On 7 April 2016

Re: Markers Markers

Aren't hierarchical markers good enough for that? On 7 April 2016 at 00:02, Ralph Goers wrote: > Didn’t we have this discussion several weeks ago? I don’t see a reason to > support it. > > Ralph > > On Apr 6, 2016, at 9:51 PM, Gary Gregory

[jira] [Closed] (LOG4J2-1184) NullPointerException when attempting to configure logging in custom ShutdownCallbackRegistry

[ https://issues.apache.org/jira/browse/LOG4J2-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-1184. --- Resolution: Won't Fix > NullPointerException when attempting to configure logging in custom >

[jira] [Assigned] (LOG4J2-1326) API change: add methods for logging CharSequences (was: Provide support for CharSequence parameters for low and zero-GC applications)

[ https://issues.apache.org/jira/browse/LOG4J2-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1326: --- Assignee: Remko Popma > API change: add methods for logging CharSequences (was: Provide