[GitHub] [logging-log4j2] rgoers commented on pull request #480: Master java11

rgoers commented on pull request #480: URL: https://github.com/apache/logging-log4j2/pull/480#issuecomment-877526559 Yup, Gary is correct. The 2.x releases will remain on Java 8. The 3.0 releases will require Java 11. Ralph > On Jul 9, 2021, at 11:52 AM, Remko Popma ***@***.**

[GitHub] [logging-log4j2] remkop commented on pull request #480: Master java11

remkop commented on pull request #480: URL: https://github.com/apache/logging-log4j2/pull/480#issuecomment-877475258 My bad, thanks Gary! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the spec

[GitHub] [logging-log4j2] garydgregory commented on pull request #480: Master java11

garydgregory commented on pull request #480: URL: https://github.com/apache/logging-log4j2/pull/480#issuecomment-877474665 > My understanding is that we will use the Java 11 compiler to generate Java-8 bytecode, so Log4j2 can be used with Java 8 at runtime. I do not think so, 2.x wil

[GitHub] [logging-log4j2] remkop commented on pull request #480: Master java11

remkop commented on pull request #480: URL: https://github.com/apache/logging-log4j2/pull/480#issuecomment-877473666 My understanding is that we will use the Java 11 compiler to generate Java-8 bytecode, so Log4j2 can be used with Java 8 at runtime. -- This is an automated message from t

[GitHub] [logging-log4j2] rschmitt commented on pull request #480: Master java11

rschmitt commented on pull request #480: URL: https://github.com/apache/logging-log4j2/pull/480#issuecomment-877472722 Just to confirm: does this mean that the next version of log4j2 will drop support for JDK8? -- This is an automated message from the Apache Git Service. To respond to th

[jira] [Updated] (LOG4J2-3122) Logging to Log4j2 MongoDb4 Appender get ERROR on trace, debug and info level.

[ https://issues.apache.org/jira/browse/LOG4J2-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Red Apple updated LOG4J2-3122: -- Summary: Logging to Log4j2 MongoDb4 Appender get ERROR on trace, debug and info level. (was: Logging

[jira] [Updated] (LOG4J2-3122) Logging to Log4j2 MongoDb4 Appender ERROR on trace, debug and info level.

[ https://issues.apache.org/jira/browse/LOG4J2-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Red Apple updated LOG4J2-3122: -- Fix Version/s: (was: 2.15.0) > Logging to Log4j2 MongoDb4 Appender ERROR on trace, debug and info

[GitHub] [logging-log4j2] sman-81 commented on pull request #547: LOG4J2-3121: log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlreadyExistsException

sman-81 commented on pull request #547: URL: https://github.com/apache/logging-log4j2/pull/547#issuecomment-877267982 > @sman-81, given this addresses a bug, I'd appreciate a change in `changes.xml` too. (You can use `dev="ggregory"`.) Done. I'm still new to the process 😎 I'm not sure

[GitHub] [logging-log4j2] sman-81 edited a comment on pull request #547: LOG4J2-3121: log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlreadyExistsExce

sman-81 edited a comment on pull request #547: URL: https://github.com/apache/logging-log4j2/pull/547#issuecomment-877267982 > @sman-81, given this addresses a bug, I'd appreciate a change in `changes.xml` too. (You can use `dev="ggregory"`.) Done. I'm still new to the process 😎 I

[jira] [Created] (LOG4J2-3122) Logging to Log4j2 MongoDb4 Appender ERROR on trace, debug and info level.

Red Apple created LOG4J2-3122: - Summary: Logging to Log4j2 MongoDb4 Appender ERROR on trace, debug and info level. Key: LOG4J2-3122 URL: https://issues.apache.org/jira/browse/LOG4J2-3122 Project: Log4j 2

[GitHub] [logging-log4j2] vy commented on pull request #547: LOG4J2-3121: log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlreadyExistsException

vy commented on pull request #547: URL: https://github.com/apache/logging-log4j2/pull/547#issuecomment-877256537 @sman-81, given this addresses a bug, I'd appreciate a change in `changes.xml` too. (You can use `dev="ggregory"`.) -- This is an automated message from the Apache Git Service

[GitHub] [logging-log4j2] sman-81 commented on a change in pull request #547: LOG4J2-3121: log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlreadyExist

sman-81 commented on a change in pull request #547: URL: https://github.com/apache/logging-log4j2/pull/547#discussion_r667014500 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/jmx/Server.java ## @@ -389,7 +389,15 @@ private static void registerAppenders(f

[GitHub] [logging-log4j2] garydgregory commented on a change in pull request #547: LOG4J2-3121: log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlready

garydgregory commented on a change in pull request #547: URL: https://github.com/apache/logging-log4j2/pull/547#discussion_r667002497 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/jmx/Server.java ## @@ -389,7 +389,15 @@ private static void registerAppend

[GitHub] [logging-log4j2] sman-81 opened a new pull request #547: LOG4J2-3121: log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlreadyExistsException

sman-81 opened a new pull request #547: URL: https://github.com/apache/logging-log4j2/pull/547 …e MBean re-initialization due to InstanceAlreadyExistsException -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL a

[jira] [Updated] (LOG4J2-3121) log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlreadyExistsException

[ https://issues.apache.org/jira/browse/LOG4J2-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Spann updated LOG4J2-3121: - Description: We occasionally encounter an {{InstanceAlreadyExistsException}} during log4j2 reco

[jira] [Updated] (LOG4J2-3121) log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlreadyExistsException

[ https://issues.apache.org/jira/browse/LOG4J2-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Spann updated LOG4J2-3121: - Description: We occasionally encounter an InstanceAlreadyExistsException during log4j2 reconfig

[jira] [Created] (LOG4J2-3121) log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlreadyExistsException

Markus Spann created LOG4J2-3121: Summary: log4j2 config modified at run-time may trigger incomplete MBean re-initialization due to InstanceAlreadyExistsException Key: LOG4J2-3121 URL: https://issues.apache.org/ji

[jira] [Commented] (LOG4J2-3113) Support Supplier<> in varargs log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378081#comment-17378081 ] Gary D. Gregory commented on LOG4J2-3113: - IMO, favoring the JRE for logging is

[jira] [Commented] (LOG4J2-3113) Support Supplier<> in varargs log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378075#comment-17378075 ] Carter Kozak commented on LOG4J2-3113: -- I agree with [~rgoers] that such a proposal

[jira] [Commented] (LOG4J2-3074) Add replacement parameter to mdc resolver

[ https://issues.apache.org/jira/browse/LOG4J2-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378071#comment-17378071 ] ASF subversion and git services commented on LOG4J2-3074: - Commi

[jira] [Commented] (LOG4J2-3067) Create a sequence number resolver for JsonTemplateLayout

[ https://issues.apache.org/jira/browse/LOG4J2-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378072#comment-17378072 ] ASF subversion and git services commented on LOG4J2-3067: - Commi

[jira] [Commented] (LOG4J2-3113) Support Supplier<> in varargs log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378067#comment-17378067 ] Markus Spann commented on LOG4J2-3113: -- {{System.Logger}} is public API that any ap

[jira] [Commented] (LOG4J2-3067) Create a sequence number resolver for JsonTemplateLayout

[ https://issues.apache.org/jira/browse/LOG4J2-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378057#comment-17378057 ] ASF subversion and git services commented on LOG4J2-3067: - Commi

[jira] [Commented] (LOG4J2-3067) Create a sequence number resolver for JsonTemplateLayout

[ https://issues.apache.org/jira/browse/LOG4J2-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378058#comment-17378058 ] ASF subversion and git services commented on LOG4J2-3067: - Commi

[jira] [Commented] (LOG4J2-3117) Log rollover throws AccessControlException if called from an unprivileged context

[ https://issues.apache.org/jira/browse/LOG4J2-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377899#comment-17377899 ] Ralph Goers commented on LOG4J2-3117: - Note that the fix for LOG4J2-150 did not invo