[jira] [Updated] (LOG4J2-1523) Log4j 1 appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1523: - Description: Support all appenders in Log4j 1 to the extent possible and reasonable. All

Re: ThreadContextMapFilter performance

This issue should be resolved now. Sent from my iPhone > On 2016/09/20, at 15:33, Ralph Goers wrote: > > I started the release process tonight but stopped it when I noticed that the > FilterPerformanceComparison test is now taking over 200 seconds to complete. >

[jira] [Updated] (LOG4J2-1523) Log4j 1 appenders

[ https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1523: - Description: Support all appenders in Log4j 1 to the extent possible and reasonable. All

[jira] [Resolved] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1010. - Resolution: Fixed Fixed the issue by returning a constant empty map instead of creating a new

[jira] [Updated] (LOG4J2-1522) Log4j 1 layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1522: - Description: Support all layouts in Log4j 1 to the extent possible an reasonable. *

[jira] [Comment Edited] (LOG4J2-1604) Log4j2 TcpSocketServer in background

[ https://issues.apache.org/jira/browse/LOG4J2-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511665#comment-15511665 ] Gary Gregory edited comment on LOG4J2-1604 at 9/22/16 12:50 AM:

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511195#comment-15511195 ] Gary Gregory commented on LOG4J2-1259: -- OK, sounds good. > Log4j threads are leaking on Tomcat

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511185#comment-15511185 ] Gabriel Stanek commented on LOG4J2-1259: The logs that I have been pasting from shutdown are

[jira] [Reopened] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1259: -- > Log4j threads are leaking on Tomcat shutdown > > >

[jira] [Comment Edited] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510972#comment-15510972 ] Gary Gregory edited comment on LOG4J2-1259 at 9/21/16 7:50 PM: --- In your

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510972#comment-15510972 ] Gary Gregory commented on LOG4J2-1259: -- In your Log4j configuration file, please set status to TRACE

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510855#comment-15510855 ] Gabriel Stanek commented on LOG4J2-1259: Good catch on the log4j-web module. It appears I did

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510729#comment-15510729 ] Gary Gregory commented on LOG4J2-1259: -- I notice that you are not using the {{log4j-web}} module.

[jira] [Commented] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510523#comment-15510523 ] Gary Gregory commented on LOG4J2-1588: -- Hello Rainer, I'm not sure playing with thread names is

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510324#comment-15510324 ] Gabriel Stanek commented on LOG4J2-1259: My test so far have not been successful. I've used the

[jira] [Commented] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509743#comment-15509743 ] Rainer Schnitker commented on LOG4J2-1588: -- A test with log4j 2.5 was ok. This issure affects

Re: Bit twiddling in org.apache.logging.log4j.core.impl.Log4jLogEvent.hashCode()

Is there really a problem to solve here? The code to compute the hashCode for a long is actually the canonical way to do this, documented in Effective Java. FindBugs is complaining about nothing... Sent from my iPhone > On 2016/09/21, at 18:02, Gary Gregory wrote: > >

Re: Bit twiddling in org.apache.logging.log4j.core.impl.Log4jLogEvent.hashCode()

But that generates lots of temp arrays... it's just as easy to use an IDE code generator to create the methods... I'll try that tomorrow [AFK ATM] Gary On Sep 21, 2016 12:23 AM, "Greg Thomas" wrote: > Though, on reflection, (no pun intended), the Objects class *is* in

[jira] [Assigned] (LOG4J2-1604) Log4j2 TcpSocketServer in background

[ https://issues.apache.org/jira/browse/LOG4J2-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reassigned LOG4J2-1604: Assignee: Gary Gregory > Log4j2 TcpSocketServer in background >

[jira] [Commented] (LOG4J2-1604) Log4j2 TcpSocketServer in background

[ https://issues.apache.org/jira/browse/LOG4J2-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509097#comment-15509097 ] Gary Gregory commented on LOG4J2-1604: -- That sounds do-able. > Log4j2 TcpSocketServer in background

[jira] [Closed] (LOG4J2-1605) Improve error messages for TcpSocketServer and UdpSocketServer.

[ https://issues.apache.org/jira/browse/LOG4J2-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1605. Resolution: Fixed In Git master. > Improve error messages for TcpSocketServer and

[jira] [Created] (LOG4J2-1605) Improve error messages for TcpSocketServer and UdpSocketServer.

Gary Gregory created LOG4J2-1605: Summary: Improve error messages for TcpSocketServer and UdpSocketServer. Key: LOG4J2-1605 URL: https://issues.apache.org/jira/browse/LOG4J2-1605 Project: Log4j 2

Re: Bit twiddling in org.apache.logging.log4j.core.impl.Log4jLogEvent.hashCode()

Though, on reflection, (no pun intended), the Objects class *is* in Java 7; https://docs.oracle.com/javase/7/docs/api/java/util/Objects.html It makes implement .equals and .hashcode trivial; Assuming a TestClass with three fields, foo, bar and foobar, you have ... @Override public int

[jira] [Updated] (LOG4J2-1604) Log4j2 TcpSocketServer in background

[ https://issues.apache.org/jira/browse/LOG4J2-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Hillman updated LOG4J2-1604: -- Description: I've been using the log4j version 1 SocketServer in background without problem.

[jira] [Updated] (LOG4J2-1604) Log4j2 TcpSocketServer in background

[ https://issues.apache.org/jira/browse/LOG4J2-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Hillman updated LOG4J2-1604: -- Priority: Minor (was: Major) > Log4j2 TcpSocketServer in background >

[jira] [Created] (LOG4J2-1604) Log4j2 TcpSocketServer in background

Colin Hillman created LOG4J2-1604: - Summary: Log4j2 TcpSocketServer in background Key: LOG4J2-1604 URL: https://issues.apache.org/jira/browse/LOG4J2-1604 Project: Log4j 2 Issue Type:

[jira] [Commented] (LOG4J2-1051) NoClassDefFoundError when starting app on Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508885#comment-15508885 ] Frank Conover commented on LOG4J2-1051: --- My mistake. I needed the core jar.