[jira] [Created] (LOG4J2-2037) Include SLF4J in log4j-bom

Arend v. Reinersdorff created LOG4J2-2037: - Summary: Include SLF4J in log4j-bom Key: LOG4J2-2037 URL: https://issues.apache.org/jira/browse/LOG4J2-2037 Project: Log4j 2 Issue Type

[jira] [Created] (LOG4J2-2036) CompositeConfiguration with monitorInterval fails to reload full configuration

Carter Douglas Kozak created LOG4J2-2036: Summary: CompositeConfiguration with monitorInterval fails to reload full configuration Key: LOG4J2-2036 URL: https://issues.apache.org/jira/browse/LOG4J2-2036

[jira] [Commented] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16156434#comment-16156434 ] Leonid Bogdanov commented on LOG4J2-2034: - BTW, a serialization exception is logged by Log4j

[jira] [Created] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

Leonid Bogdanov created LOG4J2-2035: --- Summary: There is no such lib as disruptor-3.3.3 Key: LOG4J2-2035 URL: https://issues.apache.org/jira/browse/LOG4J2-2035 Project: Log4j 2 Issue Type

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Description: When async logging is configured, JsonLayout cannot serialize a log event

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Attachment: log4j-issue.zip Demo project which reproduces the issue > In async m

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Description: When async logging is configured, JsonLayout cannot serialize a log event

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Summary: In async mode JsonLayout can't serialize an event with self referenced throwable

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Affects Version/s: 2.8.2 > In async mode JsonLayout can't serialize an event with s

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Description: When async logging is configured, JsonLayout cannot serialize a log event

[jira] [Created] (LOG4J2-2034) in async mode JsonLayout can't serialize an event with self referenced throwable

Leonid Bogdanov created LOG4J2-2034: --- Summary: in async mode JsonLayout can't serialize an event with self referenced throwable Key: LOG4J2-2034 URL: https://issues.apache.org/jira/browse/LOG4J2-2034

[jira] [Commented] (LOG4J2-2033) Regression in ProviderUtil.hasProviders for 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155887#comment-16155887 ] Andre Burgoyne commented on LOG4J2-2033: I verified that the issue is resolved using the code

[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=16155529#comment-16155529 ] member sound commented on LOG4J2-1259: -- I can confirm adding log4j-web*.jar to jarsToSkip fixes

[jira] [Updated] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2031: - Fix Version/s: (was: 2.9.1) > Log4j2 log file not reflecting application log function ca

[jira] [Commented] (LOG4J2-1769) JsonLayout Throwing Exceptions And Producing Broken Logs

[ https://issues.apache.org/jira/browse/LOG4J2-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155202#comment-16155202 ] Gabriel Klappenbach commented on LOG4J2-1769: - I don't see 2.7.1 in maven central repository

[jira] [Commented] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154970#comment-16154970 ] Colin McDowell commented on LOG4J2-2031: Appreciate you taking time to look at the issue Remko

[jira] [Assigned] (LOG4J2-2033) Regression in ProviderUtil.hasProviders for 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-2033: --- Assignee: Ralph Goers > Regression in ProviderUtil.hasProviders for 2.

[jira] [Comment Edited] (LOG4J2-2033) Regression in ProviderUtil.hasProviders for 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154451#comment-16154451 ] Andre Burgoyne edited comment on LOG4J2-2033 at 9/5/17 10:38 PM

[jira] [Commented] (LOG4J2-2033) Regression in ProviderUtil.hasProviders for 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154451#comment-16154451 ] Andre Burgoyne commented on LOG4J2-2033: Included below is my sample build.xml used for showing

[jira] [Created] (LOG4J2-2033) Regression in ProviderUtil.hasProviders for 2.9.0

Andre Burgoyne created LOG4J2-2033: -- Summary: Regression in ProviderUtil.hasProviders for 2.9.0 Key: LOG4J2-2033 URL: https://issues.apache.org/jira/browse/LOG4J2-2033 Project: Log4j 2

[jira] [Updated] (LOG4J2-2027) File appenders fail to configure when using a header with createOnDemand=true

[ https://issues.apache.org/jira/browse/LOG4J2-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-2027: --- Affects Version/s: 2.9.0 > File appenders fail to configure when using a hea

[jira] [Comment Edited] (LOG4J2-2030) ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154149#comment-16154149 ] Gary Gregory edited comment on LOG4J2-2030 at 9/5/17 7:21 PM

[jira] [Comment Edited] (LOG4J2-2030) ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154149#comment-16154149 ] jncharpin edited comment on LOG4J2-2030 at 9/5/17 7:14 PM: --- This is the stack

[jira] [Resolved] (LOG4J2-1936) ClassNotFoundException when making all loggers asynchronous under OSGi environment

[ https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1936. -- Resolution: Fixed Fix Version/s: 2.9.1 In Git master. Please verify and close

[jira] [Commented] (LOG4J2-1936) ClassNotFoundException when making all loggers asynchronous under OSGi environment

[ https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154134#comment-16154134 ] ASF subversion and git services commented on LOG4J2-1936: - Commit

[jira] [Updated] (LOG4J2-1936) ClassNotFoundException when making all loggers asynchronous under OSGi environment

[ https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1936: - Description: Can't find AsyncLoggerContextSelector when making all Log4j loggers asynchronous

[jira] [Commented] (LOG4J2-2030) ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154122#comment-16154122 ] Ralph Goers commented on LOG4J2-2030: - It didn't occur to me to leave the old version of the binding

[jira] [Commented] (LOG4J2-2030) ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154096#comment-16154096 ] Gary Gregory commented on LOG4J2-2030: -- Do you have the stack trace? > ClassCastExcept

[jira] [Commented] (LOG4J2-2027) File appenders fail to configure when using a header with createOnDemand=true

[ https://issues.apache.org/jira/browse/LOG4J2-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154012#comment-16154012 ] Gary Gregory commented on LOG4J2-2027: -- [~pburrowesOC]: Thank you for looking at this area

[jira] [Comment Edited] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153768#comment-16153768 ] Remko Popma edited comment on LOG4J2-2031 at 9/5/17 3:29 PM: - I haven't

[jira] [Comment Edited] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153768#comment-16153768 ] Remko Popma edited comment on LOG4J2-2031 at 9/5/17 3:27 PM: - I haven't

[jira] [Commented] (LOG4J2-2030) ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153824#comment-16153824 ] jncharpin commented on LOG4J2-2030: --- I just noticed the {{ServiceLoader}} approach in 2.9.0. The use

[jira] [Commented] (LOG4J2-2032) Curly braces in parameters are treated as placeholders

[ https://issues.apache.org/jira/browse/LOG4J2-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153794#comment-16153794 ] Kostiantyn Shchepanovskyi commented on LOG4J2-2032: --- Call chain: {code

[jira] [Commented] (LOG4J2-2032) Curly braces in parameters are treated as placeholders

[ https://issues.apache.org/jira/browse/LOG4J2-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153792#comment-16153792 ] Kostiantyn Shchepanovskyi commented on LOG4J2-2032: --- It seems that placeholders

[jira] [Comment Edited] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153768#comment-16153768 ] Remko Popma edited comment on LOG4J2-2031 at 9/5/17 3:01 PM: - I haven't

[jira] [Commented] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153768#comment-16153768 ] Remko Popma commented on LOG4J2-2031: - I haven't looked in great detail, but some initial

[jira] [Created] (LOG4J2-2032) Curly braces in parameters are treated as placeholders

Kostiantyn Shchepanovskyi created LOG4J2-2032: - Summary: Curly braces in parameters are treated as placeholders Key: LOG4J2-2032 URL: https://issues.apache.org/jira/browse/LOG4J2-2032

[jira] [Updated] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McDowell updated LOG4J2-2031: --- Attachment: CapacityTest.java log4j2.xml pom2.xml > Log

[jira] [Created] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

Colin McDowell created LOG4J2-2031: -- Summary: Log4j2 log file not reflecting application log function calls Key: LOG4J2-2031 URL: https://issues.apache.org/jira/browse/LOG4J2-2031 Project: Log4j 2

[jira] [Created] (LOG4J2-2030) ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

://issues.apache.org/jira/browse/LOG4J2-2030 Project: Log4j 2 Issue Type: Bug Components: Core Affects Versions: 2.9.0 Reporter: jncharpin When upgrading from 2.8.2 to 2.9.0, we are facing the following exception when accessing the context. Caused

[jira] [Commented] (LOG4J2-2027) File appenders fail to configure when using a header with createOnDemand=true

[ https://issues.apache.org/jira/browse/LOG4J2-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153110#comment-16153110 ] Ralph Goers commented on LOG4J2-2027: - Prior to the addition of createOnDemand writing the header

[jira] [Commented] (LOG4J2-2027) File appenders fail to configure when using a header with createOnDemand=true

[ https://issues.apache.org/jira/browse/LOG4J2-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153086#comment-16153086 ] Paul Burrowes commented on LOG4J2-2027: --- Still broken. I have a few possible approaches for fixing

[jira] [Updated] (LOG4J2-1936) ClassNotFoundException when making all loggers asynchronous under OSGi environment

[ https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helber Belmiro updated LOG4J2-1936: --- Attachment: patch.diff Proposed patch. > ClassNotFoundException when making all logg

[jira] [Closed] (LOG4J2-2028) Stack locator calc location is broken on JDK 9 in 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Tedor closed LOG4J2-2028. --- > Stack locator calc location is broken on JDK 9 in 2.

[jira] [Resolved] (LOG4J2-2028) Stack locator calc location is broken on JDK 9 in 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2028. - Resolution: Fixed Fix Version/s: 2.9.1 Thanks for the patch. It has been applied. Please

[jira] [Commented] (LOG4J2-2028) Stack locator calc location is broken on JDK 9 in 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152218#comment-16152218 ] ASF subversion and git services commented on LOG4J2-2028: - Commit

[jira] [Commented] (LOG4J2-2029) Marker examples should not use deprecate flow APIs

[ https://issues.apache.org/jira/browse/LOG4J2-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151614#comment-16151614 ] ASF subversion and git services commented on LOG4J2-2029: - Commit

[jira] [Closed] (LOG4J2-2029) Marker examples should not use deprecate flow APIs

[ https://issues.apache.org/jira/browse/LOG4J2-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2029. Resolution: Fixed In git master. > Marker examples should not use deprecate flow A

[jira] [Created] (LOG4J2-2029) Marker examples should not use deprecate flow APIs

Gary Gregory created LOG4J2-2029: Summary: Marker examples should not use deprecate flow APIs Key: LOG4J2-2029 URL: https://issues.apache.org/jira/browse/LOG4J2-2029 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151243#comment-16151243 ] Remko Popma commented on LOG4J2-1896: - Okay, I will take a look at this. > Update clas

[jira] [Assigned] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1896: --- Assignee: Remko Popma (was: Gary Gregory) > Update clas

[jira] [Commented] (LOG4J2-2027) File appenders fail to configure when using a header with createOnDemand=true

[ https://issues.apache.org/jira/browse/LOG4J2-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150990#comment-16150990 ] Mikael Ståldal commented on LOG4J2-2027: Can you test this on the recently released 2.9.0

[jira] [Comment Edited] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150873#comment-16150873 ] Gary Gregory edited comment on LOG4J2-2026 at 9/1/17 5:45 PM: -- The change

[jira] [Resolved] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-2026. -- Resolution: Fixed Now handling {{LinkageError}} in git master. Please verify and close

[jira] [Updated] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2026: - Description: Hi, Tested 2.9.0 RC1 and noticed one issue due to xerces 2.6.2 version being used

[jira] [Commented] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150911#comment-16150911 ] ASF subversion and git services commented on LOG4J2-2026: - Commit

[jira] [Comment Edited] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150906#comment-16150906 ] Gary Gregory edited comment on LOG4J2-2026 at 9/1/17 5:40 PM: -- Reopening

[jira] [Reopened] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-2026: -- Reopening to hanle LinkageError > java.lang.AbstractMethodEr

[jira] [Commented] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150873#comment-16150873 ] Leon Finker commented on LOG4J2-2026: - The change doesn't handle AbstractMethodError which

[jira] [Commented] (LOG4J2-2028) Stack locator calc location is broken on JDK 9 in 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150800#comment-16150800 ] ASF GitHub Bot commented on LOG4J2-2028: Github user jasontedor commented on the issue

[jira] [Created] (LOG4J2-2028) Stack locator calc location is broken on JDK 9 in 2.9.0

Jason Tedor created LOG4J2-2028: --- Summary: Stack locator calc location is broken on JDK 9 in 2.9.0 Key: LOG4J2-2028 URL: https://issues.apache.org/jira/browse/LOG4J2-2028 Project: Log4j 2

[jira] [Commented] (LOG4NET-538) AdoNetAppender to PostgreSQL

[ https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150177#comment-16150177 ] Dominik Psenner commented on LOG4NET-538: - The [build|https://builds.apache.org/job/logging

[jira] [Commented] (LOG4J2-1961) Reconfigure breaks DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150163#comment-16150163 ] Christian Vent commented on LOG4J2-1961: Sure, I'm using MacOS Sierra (10.12.x). {noformat} Java

[jira] [Commented] (LOG4NET-538) AdoNetAppender to PostgreSQL

[ https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150152#comment-16150152 ] Dominik Psenner commented on LOG4NET-538: - Awesome! Two brains reaching the same conclusion

[jira] [Comment Edited] (LOG4NET-538) AdoNetAppender to PostgreSQL

[ https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150150#comment-16150150 ] Simon Evieux edited comment on LOG4NET-538 at 9/1/17 7:12 AM: -- sorry, you

[jira] [Commented] (LOG4NET-538) AdoNetAppender to PostgreSQL

[ https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150150#comment-16150150 ] Simon Evieux commented on LOG4NET-538: -- sorry, you were faster than me :) > AdoNetAppen

[jira] [Commented] (LOG4NET-538) AdoNetAppender to PostgreSQL

[ https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150149#comment-16150149 ] Simon Evieux commented on LOG4NET-538: -- Sorry... You are right... I have not been really careful

[jira] [Commented] (LOG4NET-538) AdoNetAppender to PostgreSQL

[ https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150148#comment-16150148 ] Dominik Psenner commented on LOG4NET-538: - I just refactored the method. The second patch changes

[jira] [Commented] (LOG4NET-538) AdoNetAppender to PostgreSQL

[ https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150140#comment-16150140 ] Dominik Psenner commented on LOG4NET-538: - I patched your suggestion in the feature branch

[jira] [Commented] (LOG4NET-538) AdoNetAppender to PostgreSQL

[ https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150111#comment-16150111 ] Simon Evieux commented on LOG4NET-538: -- OK...I think I got it... In the AdoNetAppender

[jira] [Created] (LOG4J2-2027) File appenders fail to configure when using a header with createOnDemand=true

Paul Burrowes created LOG4J2-2027: - Summary: File appenders fail to configure when using a header with createOnDemand=true Key: LOG4J2-2027 URL: https://issues.apache.org/jira/browse/LOG4J2-2027

[jira] [Commented] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149646#comment-16149646 ] Jason Tedor commented on LOG4J2-2023: - The solution you have committed will work for me. It might

[jira] [Commented] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149598#comment-16149598 ] ASF subversion and git services commented on LOG4J2-2023: - Commit

[jira] [Commented] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149597#comment-16149597 ] ASF subversion and git services commented on LOG4J2-2023: - Commit

[jira] [Commented] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149593#comment-16149593 ] ASF subversion and git services commented on LOG4J2-2023: - Commit

[jira] [Commented] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149573#comment-16149573 ] ASF subversion and git services commented on LOG4J2-2023: - Commit

[jira] [Closed] (LOG4J2-1854) Gelf TCP endpoint

[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1854. -- > Gelf TCP endpoint > -- > > Key:

[jira] [Closed] (LOG4J2-1442) Add generic HTTP verb appender

[ https://issues.apache.org/jira/browse/LOG4J2-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1442. -- > Add generic HTTP verb appender > -- > >

[jira] [Closed] (LOG4J2-1923) JSONLayout should allow stacktrace as string

[ https://issues.apache.org/jira/browse/LOG4J2-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1923. -- > JSONLayout should allow stacktrace as str

[jira] [Closed] (LOG4J2-1867) jackson-databind dependency missing in the configuration document

[ https://issues.apache.org/jira/browse/LOG4J2-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1867. -- > jackson-databind dependency missing in the configuration docum

[jira] [Closed] (LOG4J2-1958) Deprecate SerializedLayout and remove it as default

[ https://issues.apache.org/jira/browse/LOG4J2-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1958. -- > Deprecate SerializedLayout and remove it as defa

[jira] [Closed] (LOG4J2-1981) JsonLayout, XmlLayout and YamlLayout should support 0-byte termination of log events

[ https://issues.apache.org/jira/browse/LOG4J2-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1981. -- > JsonLayout, XmlLayout and YamlLayout should support 0-byte termination of log >

[jira] [Closed] (LOG4J2-2020) Remove default layout from KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-2020. -- > Remove default layout from KafkaAppen

[jira] [Resolved] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-2023. -- Resolution: Fixed Fix Version/s: 2.9.1 In git master. Please verify and close

[jira] [Updated] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2023: - Description: Use a class' canonical name instead of name to create its logger name. Say you

[jira] [Reopened] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-2023: -- Reopening to adjust for a null cannonical name. > Use a class' canonical name instead of n

[jira] [Commented] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149306#comment-16149306 ] Jason Tedor commented on LOG4J2-2023: - That fix would be acceptable to me. > Use a class' canoni

[jira] [Commented] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149304#comment-16149304 ] ASF subversion and git services commented on LOG4J2-2026: - Commit

[jira] [Commented] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149294#comment-16149294 ] Gary Gregory commented on LOG4J2-2023: -- Using custom separators was discussed and rejected. The fix

[jira] [Updated] (LOG4J2-2008) RFC5424Layout should support multiple StructuredData elements.

[ https://issues.apache.org/jira/browse/LOG4J2-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2008: Fix Version/s: (was: 2.9.1) 2.9.0 > RFC5424Layout should support multi

[jira] [Closed] (LOG4J2-2008) RFC5424Layout should support multiple StructuredData elements.

[ https://issues.apache.org/jira/browse/LOG4J2-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2008. --- > RFC5424Layout should support multiple StructuredData eleme

[jira] [Resolved] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-2026. -- Resolution: Fixed Fix Version/s: 2.9.1 In git master. Any exceptions aside from

[jira] [Updated] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1990: - Fix Version/s: (was: 2.9.0) 2.9.1 > ConcurrentModificationExcept

[jira] [Updated] (LOG4J2-1630) Unit of Work Logging

[ https://issues.apache.org/jira/browse/LOG4J2-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1630: - Fix Version/s: (was: 2.9.0) 2.9.1 > Unit of Work Logg

[jira] [Updated] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1896: - Fix Version/s: (was: 2.9.0) 2.9.1 > Update clas

[jira] [Updated] (LOG4J2-2008) RFC5424Layout should support multiple StructuredData elements.

[ https://issues.apache.org/jira/browse/LOG4J2-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2008: - Fix Version/s: (was: 2.9.0) 2.9.1 > RFC5424Layout should support multi

[jira] [Updated] (LOG4J2-2026) java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature()

[ https://issues.apache.org/jira/browse/LOG4J2-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2026: - Summary: java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature

[jira] [Resolved] (LOG4J2-1480) CronTriggeringPolicy timing / file deletion issue

[ https://issues.apache.org/jira/browse/LOG4J2-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1480. - Resolution: Fixed Marking as resolved based on user feedback. Please verify and close or reopen

[jira] [Commented] (LOG4J2-1480) CronTriggeringPolicy timing / file deletion issue

[ https://issues.apache.org/jira/browse/LOG4J2-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149100#comment-16149100 ] Joseph Smith commented on LOG4J2-1480: -- I've updated to 2.8.2 and am programmatically creating

[jira] [Commented] (LOG4J2-2023) Use a class' canonical name instead of name to create its logger name

[ https://issues.apache.org/jira/browse/LOG4J2-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149047#comment-16149047 ] Jason Tedor commented on LOG4J2-2023: - Also, I want to thank you for your quick response and the link

<    1   2   3   4   5   6   7   8   9   10   >