[jira] [Comment Edited] (LOG4J2-2077) Update from Jackson 2.9.1 to 2.9.2

[ https://issues.apache.org/jira/browse/LOG4J2-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206412#comment-16206412 ] Gary Gregory edited comment on LOG4J2-2077 at 10/16/17 7:04 PM: Currently

[jira] [Commented] (LOG4J2-2077) Update from Jackson 2.9.1 to 2.9.2

[ https://issues.apache.org/jira/browse/LOG4J2-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206412#comment-16206412 ] Gary Gregory commented on LOG4J2-2077: -- Currently fails. Reported to Jackson as

[jira] [Commented] (LOG4J2-2079) Update Conversant Disruptor from 1.12.10 to 1.12.11

[ https://issues.apache.org/jira/browse/LOG4J2-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208174#comment-16208174 ] Gary Gregory commented on LOG4J2-2079: -- I'd rather wait until we switch to java 8. Less to maintain

[jira] [Commented] (LOG4J2-2087) Property log4j.skipJansi should have a default of true

[ https://issues.apache.org/jira/browse/LOG4J2-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215781#comment-16215781 ] Gary Gregory commented on LOG4J2-2087: -- ARG! > Property log4j.skipJansi should have a default of

[jira] [Commented] (LOG4J2-2089) [TagLib] Update servlet-api provided dependency from 2.5 to 3.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215552#comment-16215552 ] Gary Gregory commented on LOG4J2-2089: -- There is no hard dependencies on the servlet 3.0 API. This

[jira] [Created] (LOG4J2-2132) Update ZeroMQ's jeromq from 0.4.2 to 0.4.3

Gary Gregory created LOG4J2-2132: Summary: Update ZeroMQ's jeromq from 0.4.2 to 0.4.3 Key: LOG4J2-2132 URL: https://issues.apache.org/jira/browse/LOG4J2-2132 Project: Log4j 2 Issue Type:

[jira] [Closed] (LOG4J2-2132) Update ZeroMQ's jeromq from 0.4.2 to 0.4.3

[ https://issues.apache.org/jira/browse/LOG4J2-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2132. Resolution: Fixed Fix Version/s: 2.10.1 In Git master. > Update ZeroMQ's jeromq from 0.4.2

[jira] [Comment Edited] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276045#comment-16276045 ] Gary Gregory edited comment on LOG4J2-2133 at 12/3/17 7:38 PM: --- With KISS I

[jira] [Closed] (LOG4J2-2154) Support resetting log levels

[ https://issues.apache.org/jira/browse/LOG4J2-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2154. Resolution: Not A Bug Jira is not a support forum. May you please ask your question on our user's

[jira] [Created] (LOG4J2-2149) Update Jackson from 2.9.2 to 2.9.3

Gary Gregory created LOG4J2-2149: Summary: Update Jackson from 2.9.2 to 2.9.3 Key: LOG4J2-2149 URL: https://issues.apache.org/jira/browse/LOG4J2-2149 Project: Log4j 2 Issue Type: Improvement

[jira] [Commented] (LOG4J2-1419) Memory leak on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291598#comment-16291598 ] Gary Gregory commented on LOG4J2-1419: -- Is 2.10.0 the same? > Memory leak on Tomcat shutdown >

[jira] [Reopened] (LOG4J2-2116) Update Scala from 2.12.3 to 2.12.4

[ https://issues.apache.org/jira/browse/LOG4J2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-2116: -- > Update Scala from 2.12.3 to 2.12.4 > -- > > Key:

[jira] [Closed] (LOG4J2-2116) Update log4j-api-scala_2.12 from Scala 2.12.3 to 2.12.4

[ https://issues.apache.org/jira/browse/LOG4J2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2116. Resolution: Fixed > Update log4j-api-scala_2.12 from Scala 2.12.3 to 2.12.4 >

[jira] [Closed] (LOG4J2-2115) Update Log4j dependency from 2.8.1 to 2.9.1

[ https://issues.apache.org/jira/browse/LOG4J2-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2115. Resolution: Fixed Fix Version/s: 12.0 > Update Log4j dependency from 2.8.1 to 2.9.1 >

[jira] [Created] (LOG4J2-2116) Update Scala from 2.12.3 to 2.12.4

Gary Gregory created LOG4J2-2116: Summary: Update Scala from 2.12.3 to 2.12.4 Key: LOG4J2-2116 URL: https://issues.apache.org/jira/browse/LOG4J2-2116 Project: Log4j 2 Issue Type: Task

[jira] [Closed] (LOG4J2-2116) Update Scala from 2.12.3 to 2.12.4

[ https://issues.apache.org/jira/browse/LOG4J2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2116. Resolution: Fixed Fix Version/s: 12.0 > Update Scala from 2.12.3 to 2.12.4 >

[jira] [Created] (LOG4J2-2117) Jackson dependencies for 2.9.2 incorrectly bring in jackson-annotations 2.9.0 instead of 2.9.2

Gary Gregory created LOG4J2-2117: Summary: Jackson dependencies for 2.9.2 incorrectly bring in jackson-annotations 2.9.0 instead of 2.9.2 Key: LOG4J2-2117 URL: https://issues.apache.org/jira/browse/LOG4J2-2117

[jira] [Closed] (LOG4J2-2117) Jackson dependencies for 2.9.2 incorrectly bring in jackson-annotations 2.9.0 instead of 2.9.2

[ https://issues.apache.org/jira/browse/LOG4J2-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2117. Resolution: Invalid Fix Version/s: 2.10.0 In git master. > Jackson dependencies for 2.9.2

[jira] [Closed] (LOG4J2-2114) Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger

[ https://issues.apache.org/jira/browse/LOG4J2-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2114. Resolution: Fixed Fix Version/s: 2.10.0 In git master now. > Provide a native Log4j 2

[jira] [Closed] (LOG4J2-2114) Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger

[ https://issues.apache.org/jira/browse/LOG4J2-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2114. Resolution: Fixed > Provide a native Log4j 2 implementation of Eclipse Jetty's >

[jira] [Updated] (LOG4J2-2114) Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger

[ https://issues.apache.org/jira/browse/LOG4J2-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2114: - Description: Provide a native Log4j 2 implementation of Eclipse Jetty's

[jira] [Updated] (LOG4J2-2100) LevelMixIn class for Jackson is coded incorrectly

[ https://issues.apache.org/jira/browse/LOG4J2-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2100: - Description: While it works, the {{LevelMixIn}} class for Jackson is coded incorrectly and a

[jira] [Created] (LOG4J2-2100) LevelMixIn class for Jackson is coded incorrectly

Gary Gregory created LOG4J2-2100: Summary: LevelMixIn class for Jackson is coded incorrectly Key: LOG4J2-2100 URL: https://issues.apache.org/jira/browse/LOG4J2-2100 Project: Log4j 2 Issue

[jira] [Updated] (LOG4J2-2100) LevelMixIn class for Jackson is coded incorrectly

[ https://issues.apache.org/jira/browse/LOG4J2-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2100: - Description: While it works, the {{LevelMixIn}} class for Jackson is coded incorrectly and a

[jira] [Closed] (LOG4J2-2100) LevelMixIn class for Jackson is coded incorrectly

[ https://issues.apache.org/jira/browse/LOG4J2-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2100. Resolution: Fixed Fix Version/s: 2.10.0 Fixed in git master. > LevelMixIn class for

[jira] [Closed] (LOG4J2-2096) Update Apache Kafka kafka-clients from 0.11.0.1 to 1.0.0

[ https://issues.apache.org/jira/browse/LOG4J2-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2096. Resolution: Fixed Fix Version/s: 2.10.0 In git master. > Update Apache Kafka kafka-clients

[jira] [Commented] (LOG4J2-2148) CronTriggeringPolicy renaming behavior

[ https://issues.apache.org/jira/browse/LOG4J2-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287630#comment-16287630 ] Gary Gregory commented on LOG4J2-2148: -- I would start by using the current version: 2.10.0. >

[jira] [Commented] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16278782#comment-16278782 ] Gary Gregory commented on LOG4J2-2133: -- Maybe one of: - {{log4j-api-ext}} - {{log4j-api-plus}} -

[jira] [Closed] (LOG4J2-2334) Add API org.apache.logging.log4j.core.appender.AsyncAppender.getQueueSize()

[ https://issues.apache.org/jira/browse/LOG4J2-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2334. Resolution: Fixed Fix Version/s: 2.11.1 3.0.0 In git {{master}} and

[jira] [Created] (LOG4J2-2334) Add API org.apache.logging.log4j.core.appender.AsyncAppender.getQueueSize()

Gary Gregory created LOG4J2-2334: Summary: Add API org.apache.logging.log4j.core.appender.AsyncAppender.getQueueSize() Key: LOG4J2-2334 URL: https://issues.apache.org/jira/browse/LOG4J2-2334 Project:

[jira] [Commented] (LOG4J2-2340) Do not print stack trace when environment variables access is restricted

[ https://issues.apache.org/jira/browse/LOG4J2-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476007#comment-16476007 ] Gary Gregory commented on LOG4J2-2340: -- I can't say this really makes sense to me. It seems like

[jira] [Comment Edited] (LOG4J2-2340) Do not print stack trace when environment variables access is restricted

[ https://issues.apache.org/jira/browse/LOG4J2-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476007#comment-16476007 ] Gary Gregory edited comment on LOG4J2-2340 at 5/15/18 3:33 PM: --- I can't say

[jira] [Comment Edited] (LOG4J2-2340) Do not print stack trace when environment variables access is restricted

[ https://issues.apache.org/jira/browse/LOG4J2-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476007#comment-16476007 ] Gary Gregory edited comment on LOG4J2-2340 at 5/15/18 3:29 PM: --- I can't say

[jira] [Commented] (LOG4J2-2351) AbstractLogEvent.instant should be protected, not private

[ https://issues.apache.org/jira/browse/LOG4J2-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509904#comment-16509904 ] Gary Gregory commented on LOG4J2-2351: -- Have you considered adding a protected getMutableInstant()

[jira] [Created] (LOG4J2-2347) Update Apache Commons Compress from 1.16.1 to 1.17

Gary Gregory created LOG4J2-2347: Summary: Update Apache Commons Compress from 1.16.1 to 1.17 Key: LOG4J2-2347 URL: https://issues.apache.org/jira/browse/LOG4J2-2347 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-2283) ParserConfigurationException when using Log4j with oracle.xml.jaxp.JXDocumentBuilderFactory

[ https://issues.apache.org/jira/browse/LOG4J2-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528005#comment-16528005 ] Gary Gregory commented on LOG4J2-2283: -- Is https://thecattlecrew.net/2014/11/25/1334/ in our list

[jira] [Commented] (LOG4J2-2283) ParserConfigurationException when using Log4j with oracle.xml.jaxp.JXDocumentBuilderFactory

[ https://issues.apache.org/jira/browse/LOG4J2-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523953#comment-16523953 ] Gary Gregory commented on LOG4J2-2283: -- The code currently catches and prints that exception, then

[jira] [Closed] (LOG4J2-2357) Update Jackson from 2.9.5 to 2.9.6.

[ https://issues.apache.org/jira/browse/LOG4J2-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2357. Resolution: Fixed Fix Version/s: 2.11.1 3.0.0 In git master. > Update

[jira] [Created] (LOG4J2-2357) Update Jackson from 2.9.5 to 2.9.6.

Gary Gregory created LOG4J2-2357: Summary: Update Jackson from 2.9.5 to 2.9.6. Key: LOG4J2-2357 URL: https://issues.apache.org/jira/browse/LOG4J2-2357 Project: Log4j 2 Issue Type:

[jira] [Closed] (LOG4J2-2358) Update Kafka client from 1.0.0 to 1.1.0.

[ https://issues.apache.org/jira/browse/LOG4J2-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2358. Resolution: Fixed Assignee: Gary Gregory Fix Version/s: 2.11.1

[jira] [Created] (LOG4J2-2358) Update Kafka client from 1.0.0 to 1.1.0.

Gary Gregory created LOG4J2-2358: Summary: Update Kafka client from 1.0.0 to 1.1.0. Key: LOG4J2-2358 URL: https://issues.apache.org/jira/browse/LOG4J2-2358 Project: Log4j 2 Issue Type:

[jira] [Created] (LOG4J2-2327) java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource: Provider

Gary Gregory created LOG4J2-2327: Summary: java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource: Provider Key: LOG4J2-2327 URL: https://issues.apache.org/jira/browse/LOG4J2-2327

[jira] [Updated] (LOG4J2-2327) java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource: Provider org.apache.logging.log4j.util.EnvironmentPropertySource not a subtype

[ https://issues.apache.org/jira/browse/LOG4J2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2327: - Summary: java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource:

[jira] [Closed] (LOG4J2-2327) java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource: Provider org.apache.logging.log4j.util.EnvironmentPropertySource not a subtype

[ https://issues.apache.org/jira/browse/LOG4J2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2327. Resolution: Fixed Fix Version/s: 3.0.0 In git {{master}} and {{release-2.x}}. >

[jira] [Commented] (LOG4J2-2173) JMS Appender is not re-connecting on JBoss

[ https://issues.apache.org/jira/browse/LOG4J2-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454450#comment-16454450 ] Gary Gregory commented on LOG4J2-2173: -- Please post back here with your progress but first make sure

[jira] [Commented] (LOG4J2-2173) JMS Appender is not re-connecting on JBoss

[ https://issues.apache.org/jira/browse/LOG4J2-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454421#comment-16454421 ] Gary Gregory commented on LOG4J2-2173: -- I created LOG4J2-2173 to track the fix for

[jira] [Updated] (LOG4J2-2327) java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource: Provider org.apache.logging.log4j.util.EnvironmentPropertySource not a subtype

[ https://issues.apache.org/jira/browse/LOG4J2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2327: - Description: java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource:

[jira] [Updated] (LOG4J2-2327) java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource: Provider

[ https://issues.apache.org/jira/browse/LOG4J2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2327: - Description: java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource:

[jira] [Commented] (LOG4J2-2327) java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource: Provider org.apache.logging.log4j.util.EnvironmentPropertySource not a subtype

[ https://issues.apache.org/jira/browse/LOG4J2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454855#comment-16454855 ] Gary Gregory commented on LOG4J2-2327: -- It seems to be that the error message reported

[jira] [Comment Edited] (LOG4J2-2327) java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource: Provider org.apache.logging.log4j.util.EnvironmentPropertySource not a subtype

[ https://issues.apache.org/jira/browse/LOG4J2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454855#comment-16454855 ] Gary Gregory edited comment on LOG4J2-2327 at 4/26/18 8:53 PM: --- It seems to

[jira] [Commented] (LOG4J2-2329) Fix dependency in log4j-slf4j-impl to slf4j due to CVE-2018-8088

[ https://issues.apache.org/jira/browse/LOG4J2-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458983#comment-16458983 ] Gary Gregory commented on LOG4J2-2329: -- What happens when you do a build with the new dependency? >

[jira] [Closed] (LOG4J2-2089) [TagLib] Update servlet-api provided dependency from 2.5 to 3.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2089. Resolution: Fixed Fix Version/s: 12.0 > [TagLib] Update servlet-api provided dependency

[jira] [Reopened] (LOG4J2-2089) [TagLib] Update servlet-api provided dependency from 2.5 to 3.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-2089: -- > [TagLib] Update servlet-api provided dependency from 2.5 to 3.0.1 >

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

[ https://issues.apache.org/jira/browse/LOG4J2-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307095#comment-16307095 ] Gary Gregory commented on LOG4J2-2036: -- Dang, I lost track of this issue. I'll try to take a look

[jira] [Created] (LOG4J2-2165) Update Jackson from 2.9.2 to 2.9.3

Gary Gregory created LOG4J2-2165: Summary: Update Jackson from 2.9.2 to 2.9.3 Key: LOG4J2-2165 URL: https://issues.apache.org/jira/browse/LOG4J2-2165 Project: Log4j 2 Issue Type: Improvement

[jira] [Commented] (LOG4J2-2162) KafkaAppender fails application startup when bootstrap server are not available

[ https://issues.apache.org/jira/browse/LOG4J2-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312099#comment-16312099 ] Gary Gregory commented on LOG4J2-2162: -- Roger that. I'm not there yet ;-) > KafkaAppender fails

[jira] [Created] (LOG4J2-2177) Update use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

Gary Gregory created LOG4J2-2177: Summary: Update use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map) Key: LOG4J2-2177 URL:

[jira] [Updated] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2177: - Description: Replace use of deprecated Core API

[jira] [Updated] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2177: - Summary: Replace use of deprecated Core API

[jira] [Commented] (LOG4J2-2178) Log4j2 ThreadNameCachingStrategy CACHED vs UNCACHED alternative

[ https://issues.apache.org/jira/browse/LOG4J2-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312054#comment-16312054 ] Gary Gregory commented on LOG4J2-2178: -- Thank you for you request. Maybe we need to abstract that

[jira] [Updated] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2177: - Description: Replace use of deprecated Core API

[jira] [Commented] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314786#comment-16314786 ] Gary Gregory commented on LOG4J2-2177: -- Like it says on the tin, the goal here is to remove use of

[jira] [Issue Comment Deleted] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2177: - Comment: was deleted (was: Let me take some time this weekend to study this some more...) >

[jira] [Resolved] (LOG4J2-2157) Don't create exit message in traceExit(R) when logging is disabled

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

[jira] [Assigned] (LOG4J2-2157) Don't create exit message in traceExit(R) when logging is disabled

[ https://issues.apache.org/jira/browse/LOG4J2-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reassigned LOG4J2-2157: Assignee: Gary Gregory > Don't create exit message in traceExit(R) when logging is

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315413#comment-16315413 ] Gary Gregory commented on LOG4J2-1883: -- That's a Java 8 API BTW even though the precision is best on

[jira] [Commented] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317655#comment-16317655 ] Gary Gregory commented on LOG4J2-2177: -- Hi [~rem...@yahoo.com], yes of course. I did not know it was

[jira] [Commented] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317449#comment-16317449 ] Gary Gregory commented on LOG4J2-2177: -- I also went to using StringMap instead of IndexedStringMap

[jira] [Commented] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313352#comment-16313352 ] Gary Gregory commented on LOG4J2-2177: -- [~mikaelstaldal]: I fixed the message. Question: We only

[jira] [Updated] (LOG4J2-2171) Log4j2 is not embeddable due to its system classloader usage

[ https://issues.apache.org/jira/browse/LOG4J2-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2171: - Description: Hi guys, in several places, log4j2 enforces the system classloader to be used. I

[jira] [Updated] (LOG4J2-2179) The MongoDB Appender should use keys and values from a Log4j MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2179: - Summary: The MongoDB Appender should use keys and values from a Log4j MapMessage (was: The

[jira] [Closed] (LOG4J2-2179) The MongoDB Appender should use keys and values from a Log4j MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2179. Resolution: Fixed > The MongoDB Appender should use keys and values from a Log4j MapMessage >

[jira] [Closed] (LOG4J2-2179) The MongoDB Appender should use a keys and values for a Log4j MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2179. Resolution: Fixed Fix Version/s: 2.10.1 In git master. > The MongoDB Appender should use a

[jira] [Closed] (LOG4J2-2180) Add a MongoDbProvider builder for and deprecate org.apache.logging.log4j.mongodb.MongoDbProvider.createNoSqlProvider()

[ https://issues.apache.org/jira/browse/LOG4J2-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2180. Resolution: Fixed Fix Version/s: 2.10.1 In git master. > Add a MongoDbProvider builder for

[jira] [Created] (LOG4J2-2181) The JDBC Appender should use keys and values from a Log4j MapMessage

Gary Gregory created LOG4J2-2181: Summary: The JDBC Appender should use keys and values from a Log4j MapMessage Key: LOG4J2-2181 URL: https://issues.apache.org/jira/browse/LOG4J2-2181 Project: Log4j

[jira] [Commented] (LOG4J2-2162) KafkaAppender fails application startup when bootstrap server are not available

[ https://issues.apache.org/jira/browse/LOG4J2-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311610#comment-16311610 ] Gary Gregory commented on LOG4J2-2162: -- The Socket and JMS Managers both use a "Reconnector" class.

[jira] [Comment Edited] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317449#comment-16317449 ] Gary Gregory edited comment on LOG4J2-2177 at 1/9/18 12:56 AM: --- I also went

[jira] [Commented] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317437#comment-16317437 ] Gary Gregory commented on LOG4J2-2177: -- I agree with [~mikaelstaldal] and I removed the

[jira] [Resolved] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-2177. -- Resolution: Fixed Setting to resolve to signify that I think I am done. Further code review is

[jira] [Updated] (LOG4J2-2177) Replace use of deprecated Core API org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2177: - Fix Version/s: 2.10.1 > Replace use of deprecated Core API >

[jira] [Commented] (LOG4J2-2171) Log4j2 is not embeddable due to its system classloader usage

[ https://issues.apache.org/jira/browse/LOG4J2-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318632#comment-16318632 ] Gary Gregory commented on LOG4J2-2171: -- Tangents: We also have {code:java}

[jira] [Comment Edited] (LOG4J2-2178) Log4j2 ThreadNameCachingStrategy CACHED vs UNCACHED alternative

[ https://issues.apache.org/jira/browse/LOG4J2-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313865#comment-16313865 ] Gary Gregory edited comment on LOG4J2-2178 at 1/5/18 8:57 PM: -- Please

[jira] [Commented] (LOG4J2-2178) Log4j2 ThreadNameCachingStrategy CACHED vs UNCACHED alternative

[ https://issues.apache.org/jira/browse/LOG4J2-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313865#comment-16313865 ] Gary Gregory commented on LOG4J2-2178: -- Please worry about the 'right' way to provide a solution.

[jira] [Commented] (LOG4J2-2173) JMS Appender is not re-connecting on JBoss

[ https://issues.apache.org/jira/browse/LOG4J2-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328797#comment-16328797 ] Gary Gregory commented on LOG4J2-2173: -- The names of your jar files are odd. Normal Log4j JAR file

[jira] [Commented] (LOG4J2-2196) Pattern layout %notEmpty does not work for exceptions

[ https://issues.apache.org/jira/browse/LOG4J2-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331148#comment-16331148 ] Gary Gregory commented on LOG4J2-2196: -- May you please provide: * Your configuration file * The

[jira] [Created] (LOG4J2-2198) Update MongoDB dependencies from classic to modern.

Gary Gregory created LOG4J2-2198: Summary: Update MongoDB dependencies from classic to modern. Key: LOG4J2-2198 URL: https://issues.apache.org/jira/browse/LOG4J2-2198 Project: Log4j 2 Issue

[jira] [Closed] (LOG4J2-2198) Update MongoDB dependencies from classic to modern.

[ https://issues.apache.org/jira/browse/LOG4J2-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2198. Resolution: Fixed Fix Version/s: 2.11 In git master. Tested with Java 8 and 'mvn clean

[jira] [Created] (LOG4J2-2209) Rename existing MongoDb plugin to MongoDb2

Gary Gregory created LOG4J2-2209: Summary: Rename existing MongoDb plugin to MongoDb2 Key: LOG4J2-2209 URL: https://issues.apache.org/jira/browse/LOG4J2-2209 Project: Log4j 2 Issue Type:

[jira] [Closed] (LOG4J2-2206) Add method org.apache.logging.log4j.core.util.WatchManager.reset(File) and reset()

[ https://issues.apache.org/jira/browse/LOG4J2-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2206. Resolution: Fixed In git master. > Add method

[jira] [Created] (LOG4J2-2207) MongoDB provider leaks MongoClient instances

Gary Gregory created LOG4J2-2207: Summary: MongoDB provider leaks MongoClient instances Key: LOG4J2-2207 URL: https://issues.apache.org/jira/browse/LOG4J2-2207 Project: Log4j 2 Issue Type:

[jira] [Created] (LOG4J2-2205) Remove use of deprecated MongoDB APIs

Gary Gregory created LOG4J2-2205: Summary: Remove use of deprecated MongoDB APIs Key: LOG4J2-2205 URL: https://issues.apache.org/jira/browse/LOG4J2-2205 Project: Log4j 2 Issue Type:

[jira] [Updated] (LOG4J2-2205) Remove use of deprecated MongoDB APIs

[ https://issues.apache.org/jira/browse/LOG4J2-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2205: - Description: Remove use of deprecated MongoDB APIs: {noformat} Description Resource

[jira] [Updated] (LOG4J2-2207) MongoDB provider leaks MongoClient instances

[ https://issues.apache.org/jira/browse/LOG4J2-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2207: - Description: The MongoDB provider {{org.apache.logging.log4j.mongodb.MongoDbProvider}} leaks

[jira] [Updated] (LOG4J2-2186) Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 2

[ https://issues.apache.org/jira/browse/LOG4J2-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2186: - Description: Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP.

[jira] [Closed] (LOG4J2-2208) Add debug logging to org.apache.logging.log4j.mongodb.MongoDbConnection

[ https://issues.apache.org/jira/browse/LOG4J2-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2208. Resolution: Fixed Assignee: Gary Gregory Fix Version/s: 2.11.0 Closing: In git

[jira] [Created] (LOG4J2-2208) Add debug logging to org.apache.logging.log4j.mongodb.MongoDbConnection

Gary Gregory created LOG4J2-2208: Summary: Add debug logging to org.apache.logging.log4j.mongodb.MongoDbConnection Key: LOG4J2-2208 URL: https://issues.apache.org/jira/browse/LOG4J2-2208 Project:

[jira] [Created] (LOG4J2-2206) Add method org.apache.logging.log4j.core.util.WatchManager.reset(File) to

Gary Gregory created LOG4J2-2206: Summary: Add method org.apache.logging.log4j.core.util.WatchManager.reset(File) to Key: LOG4J2-2206 URL: https://issues.apache.org/jira/browse/LOG4J2-2206 Project:

[jira] [Deleted] (LOG4J2-2207) MongoDB provider leaks MongoClient instances

[ https://issues.apache.org/jira/browse/LOG4J2-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory deleted LOG4J2-2207: - > MongoDB provider leaks MongoClient instances > > >

[jira] [Updated] (LOG4J2-2206) Add method org.apache.logging.log4j.core.util.WatchManager.reset(File) and reset()

[ https://issues.apache.org/jira/browse/LOG4J2-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2206: - Summary: Add method org.apache.logging.log4j.core.util.WatchManager.reset(File) and reset()

[jira] [Closed] (LOG4J2-2204) org.apache.logging.log4j.core.util.WatchManager.getWatchers() should pre-allocate its new Map

[ https://issues.apache.org/jira/browse/LOG4J2-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2204. Resolution: Fixed Fix Version/s: 2.11.0 Closing: In git master. >

  1   2   3   4   5   6   7   >