[jira] [Resolved] (LOG4J2-3658) Add support for providing Log4j properties in JSON files

[ https://issues.apache.org/jira/browse/LOG4J2-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3658. - Resolution: Fixed Added in new 57af66b97e LOG4J2-3658 - Allow Log4j 2 properties in JSON files

[jira] [Closed] (LOG4J2-3658) Add support for providing Log4j properties in JSON files

[ https://issues.apache.org/jira/browse/LOG4J2-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-3658. --- > Add support for providing Log4j properties in JSON fi

[jira] [Created] (LOG4J2-3658) Add support for providing Log4j properties in JSON files

Ralph Goers created LOG4J2-3658: --- Summary: Add support for providing Log4j properties in JSON files Key: LOG4J2-3658 URL: https://issues.apache.org/jira/browse/LOG4J2-3658 Project: Log4j 2

[jira] [Comment Edited] (LOG4J2-2297) java.sql.Time objects are incorrectly formatted

[ https://issues.apache.org/jira/browse/LOG4J2-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706126#comment-17706126 ] Robert Turner edited comment on LOG4J2-2297 at 3/28/23 8:1

[jira] [Commented] (LOG4J2-2297) java.sql.Time objects are incorrectly formatted

[ https://issues.apache.org/jira/browse/LOG4J2-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706126#comment-17706126 ] Robert Turner commented on LOG4J2-2297: --- I'm seeing a crash in 2.20.0 n

[jira] [Closed] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat Kamalov closed LOG4J2-3657. - > Log4j memory leak via Classloader > - > >

[jira] [Resolved] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici resolved LOG4J2-3657. --- Resolution: Fixed > Log4j memory leak via Classloa

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici updated LOG4J2-3657: -- Fix Version/s: 2.21.0 > Log4j memory leak via Classloa

[jira] [Commented] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704818#comment-17704818 ] Volkan Yazici commented on LOG4J2-3657: --- Thanks so much for the report, thr

[jira] [Assigned] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici reassigned LOG4J2-3657: - Assignee: Volkan Yazici > Log4j memory leak via Classloa

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat Kamalov updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat Kamalov updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Priority: Critical (was: Major) > Log4j memory leak via Classloa

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via multiple classloaders

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via Classloader

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Summary: Log4j memory leak via Classloader (was: Log4j memory leak via multiple classloaders) > Lo

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via multiple classloaders

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via multiple classloaders

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Updated] (LOG4J2-3657) Log4j memory leak via multiple classloaders

[ https://issues.apache.org/jira/browse/LOG4J2-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat updated LOG4J2-3657: -- Description: We have a memory leak in the application. If we stop and run Jetty in the loop in JUnit we get

[jira] [Created] (LOG4J2-3657) Log4j memory leak via multiple classloaders

Marat created LOG4J2-3657: - Summary: Log4j memory leak via multiple classloaders Key: LOG4J2-3657 URL: https://issues.apache.org/jira/browse/LOG4J2-3657 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-3656) Log4j2 Rolling Logs Throwing java.nio.file.AccessDeniedException

[ https://issues.apache.org/jira/browse/LOG4J2-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704242#comment-17704242 ] Ralph Goers commented on LOG4J2-3656: - I see a few things in this configura

[jira] [Created] (LOG4J2-3656) Log4j2 Rolling Logs Throwing java.nio.file.AccessDeniedException

R.Hurley created LOG4J2-3656: Summary: Log4j2 Rolling Logs Throwing java.nio.file.AccessDeniedException Key: LOG4J2-3656 URL: https://issues.apache.org/jira/browse/LOG4J2-3656 Project: Log4j 2

[jira] [Assigned] (LOG4J2-3655) Set the ip variable in loggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici reassigned LOG4J2-3655: - Assignee: Volkan Yazici > Set the ip variable in loggerCont

[jira] [Resolved] (LOG4J2-3655) Set the ip variable in loggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici resolved LOG4J2-3655. --- Resolution: Information Provided > Set the ip variable in loggerCont

[jira] [Commented] (LOG4J2-3655) Set the ip variable in loggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702894#comment-17702894 ] Volkan Yazici commented on LOG4J2-3655: --- You can either use one of the exis

[jira] [Created] (LOG4J2-3655) Set the ip variable in loggerContext

xuwenping created LOG4J2-3655: - Summary: Set the ip variable in loggerContext Key: LOG4J2-3655 URL: https://issues.apache.org/jira/browse/LOG4J2-3655 Project: Log4j 2 Issue Type: Question

[jira] [Closed] (LOG4J2-3654) The date of the file pattern is displayed as the date of the previous day.

[ https://issues.apache.org/jira/browse/LOG4J2-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] NamHyoekJoon closed LOG4J2-3654. Resolution: Not A Bug Ticket submitted due to my misunderstanding > The date of the file patt

[jira] [Updated] (LOG4J2-3654) The date of the file pattern is displayed as the date of the previous day.

[ https://issues.apache.org/jira/browse/LOG4J2-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] NamHyoekJoon updated LOG4J2-3654: - Description: !image-2023-03-12-03-35-04-729.png! !image-2023-03-12-03-33-48-213.png

[jira] [Created] (LOG4J2-3654) The date of the file pattern is displayed as the date of the previous day.

NamHyoekJoon created LOG4J2-3654: Summary: The date of the file pattern is displayed as the date of the previous day. Key: LOG4J2-3654 URL: https://issues.apache.org/jira/browse/LOG4J2-3654 Project

[jira] [Created] (LOG4J2-3653) RollingFile TimeZone still doesn't work

NamHyoekJoon created LOG4J2-3653: Summary: RollingFile TimeZone still doesn't work Key: LOG4J2-3653 URL: https://issues.apache.org/jira/browse/LOG4J2-3653 Project: Log4j 2 Issue Type

[jira] [Commented] (LOG4J2-2808) LoggerContext should skip looking up localhost when hostName is configured.

[ https://issues.apache.org/jira/browse/LOG4J2-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696813#comment-17696813 ] Maxime Leur commented on LOG4J2-2808: - Hi, I have same issue on my product

[jira] [Commented] (LOG4J2-2678) Add LogEvent timestamp to ProducerRecord in KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696648#comment-17696648 ] Cheng Pan commented on LOG4J2-2678: --- What's the final fixed version? I see t

[jira] [Comment Edited] (LOG4J2-2870) Dependency on PropertyChangeListener and PropertyChangeEvent

[ https://issues.apache.org/jira/browse/LOG4J2-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696435#comment-17696435 ] Jannik Zuther edited comment on LOG4J2-2870 at 3/4/23 2:3

[jira] [Commented] (LOG4J2-2870) Dependency on PropertyChangeListener and PropertyChangeEvent

[ https://issues.apache.org/jira/browse/LOG4J2-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696435#comment-17696435 ] Jannik Zuther commented on LOG4J2-2870: --- Still seems to be the case in `3.0.0

[jira] [Updated] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

[ https://issues.apache.org/jira/browse/LOG4J2-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jannik Zuther updated LOG4J2-3652: -- Description: I'm trying out the current `3.0.0-SNAPSHOT` (not sure if they have a uniq

[jira] [Updated] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

[ https://issues.apache.org/jira/browse/LOG4J2-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jannik Zuther updated LOG4J2-3652: -- Description: I'm trying out the current `3.0.0-SNAPSHOT` (not sure if they have a uniq

[jira] [Updated] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

[ https://issues.apache.org/jira/browse/LOG4J2-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jannik Zuther updated LOG4J2-3652: -- Description: I'm trying out the current `3.0.0-SNAPSHOT` (that's the ones from

[jira] [Updated] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

[ https://issues.apache.org/jira/browse/LOG4J2-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jannik Zuther updated LOG4J2-3652: -- Description: I'm trying out the current `3.0.0-SNAPSHOT` (that's the ones from

[jira] [Created] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

Jannik Zuther created LOG4J2-3652: - Summary: jlink creates broken runtime image when using "--strip-debug" flag Key: LOG4J2-3652 URL: https://issues.apache.org/jira/browse/LOG4J2-3652 Proj

[jira] [Created] (LOG4J2-3651) 2.20.0 release notes change pattern confused ("for")

Philippe Cloutier created LOG4J2-3651: - Summary: 2.20.0 release notes change pattern confused ("for") Key: LOG4J2-3651 URL: https://issues.apache.org/jira/browse/LOG4J2-3651 Projec

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695304#comment-17695304 ] Piotr Karwasz commented on LOG4J2-3650: --- For future reference I'll add

[jira] [Work logged] (LOG4J2-2332) Unresolved variables in any file appender

[ https://issues.apache.org/jira/browse/LOG4J2-2332?focusedWorklogId=848243&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848243 ] ASF GitHub Bot logged work on LOG4J2-2332: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3040) ShutdownCallbackRegistry should be part of log4j-api, not log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3040?focusedWorklogId=848215&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848215 ] ASF GitHub Bot logged work on LOG4J2-3040: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3040) ShutdownCallbackRegistry should be part of log4j-api, not log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3040?focusedWorklogId=848214&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848214 ] ASF GitHub Bot logged work on LOG4J2-3040: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2332) Unresolved variables in any file appender

[ https://issues.apache.org/jira/browse/LOG4J2-2332?focusedWorklogId=848201&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848201 ] ASF GitHub Bot logged work on LOG4J2-2332: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2399) Reusable Messages do not respect log4j.format.msg.async

[ https://issues.apache.org/jira/browse/LOG4J2-2399?focusedWorklogId=848200&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848200 ] ASF GitHub Bot logged work on LOG4J2-2399: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2902) LoaderUtil#getClassLoaders throws a SecurityException trying to access system class loader

[ https://issues.apache.org/jira/browse/LOG4J2-2902?focusedWorklogId=848199&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848199 ] ASF GitHub Bot logged work on LOG4J2-2902: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3068) JCToolsBlockingQueueFactory can use MpscBlockingConsumerArrayQueue

[ https://issues.apache.org/jira/browse/LOG4J2-3068?focusedWorklogId=848197&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848197 ] ASF GitHub Bot logged work on LOG4J2-3068: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3319) Add minimal support for log4j 1.2 API bundle usage in Eclipse IDE

[ https://issues.apache.org/jira/browse/LOG4J2-3319?focusedWorklogId=848196&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848196 ] ASF GitHub Bot logged work on LOG4J2-3319: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3332) SmtpAppender: add capability to send buffered messages as an email attachment (text, zip, gzip)

[ https://issues.apache.org/jira/browse/LOG4J2-3332?focusedWorklogId=848194&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848194 ] ASF GitHub Bot logged work on LOG4J2-3332: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3040) ShutdownCallbackRegistry should be part of log4j-api, not log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3040?focusedWorklogId=848191&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848191 ] ASF GitHub Bot logged work on LOG4J2-3040: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3558) Make the default thread priority configurable

[ https://issues.apache.org/jira/browse/LOG4J2-3558?focusedWorklogId=848190&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848190 ] ASF GitHub Bot logged work on LOG4J2-3558: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3627) PatternLayout: %xEx{ [ "short" | depth]} not working

[ https://issues.apache.org/jira/browse/LOG4J2-3627?focusedWorklogId=848189&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848189 ] ASF GitHub Bot logged work on LOG4J2-3627: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2947) LogBuilder should not have no-op default methods

[ https://issues.apache.org/jira/browse/LOG4J2-2947?focusedWorklogId=848188&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848188 ] ASF GitHub Bot logged work on LOG4J2-2947: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3280) Support for microsecond precision in RFC5424Layout

[ https://issues.apache.org/jira/browse/LOG4J2-3280?focusedWorklogId=848187&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848187 ] ASF GitHub Bot logged work on LOG4J2-3280: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3280) Support for microsecond precision in RFC5424Layout

[ https://issues.apache.org/jira/browse/LOG4J2-3280?focusedWorklogId=848186&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848186 ] ASF GitHub Bot logged work on LOG4J2-3280: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3627) PatternLayout: %xEx{ [ "short" | depth]} not working

[ https://issues.apache.org/jira/browse/LOG4J2-3627?focusedWorklogId=848096&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848096 ] ASF GitHub Bot logged work on LOG4J2-3627: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2947) LogBuilder should not have no-op default methods

[ https://issues.apache.org/jira/browse/LOG4J2-2947?focusedWorklogId=848095&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848095 ] ASF GitHub Bot logged work on LOG4J2-2947: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3280) Support for microsecond precision in RFC5424Layout

[ https://issues.apache.org/jira/browse/LOG4J2-3280?focusedWorklogId=848089&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848089 ] ASF GitHub Bot logged work on LOG4J2-3280: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3040) ShutdownCallbackRegistry should be part of log4j-api, not log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3040?focusedWorklogId=848093&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848093 ] ASF GitHub Bot logged work on LOG4J2-3040: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3319) Add minimal support for log4j 1.2 API bundle usage in Eclipse IDE

[ https://issues.apache.org/jira/browse/LOG4J2-3319?focusedWorklogId=848091&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848091 ] ASF GitHub Bot logged work on LOG4J2-3319: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3068) JCToolsBlockingQueueFactory can use MpscBlockingConsumerArrayQueue

[ https://issues.apache.org/jira/browse/LOG4J2-3068?focusedWorklogId=848088&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848088 ] ASF GitHub Bot logged work on LOG4J2-3068: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3332) SmtpAppender: add capability to send buffered messages as an email attachment (text, zip, gzip)

[ https://issues.apache.org/jira/browse/LOG4J2-3332?focusedWorklogId=848092&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848092 ] ASF GitHub Bot logged work on LOG4J2-3332: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-3558) Make the default thread priority configurable

[ https://issues.apache.org/jira/browse/LOG4J2-3558?focusedWorklogId=848094&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848094 ] ASF GitHub Bot logged work on LOG4J2-3558: -- Author: ASF GitHub

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

[ https://issues.apache.org/jira/browse/LOG4J2-3122?focusedWorklogId=848090&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848090 ] ASF GitHub Bot logged work on LOG4J2-3122: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2902) LoaderUtil#getClassLoaders throws a SecurityException trying to access system class loader

[ https://issues.apache.org/jira/browse/LOG4J2-2902?focusedWorklogId=848084&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848084 ] ASF GitHub Bot logged work on LOG4J2-2902: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2954) Shutdown callbacks registered in LoggerContext.setUpShutdownHook() aren't strongly referenced

[ https://issues.apache.org/jira/browse/LOG4J2-2954?focusedWorklogId=848085&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848085 ] ASF GitHub Bot logged work on LOG4J2-2954: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2399) Reusable Messages do not respect log4j.format.msg.async

[ https://issues.apache.org/jira/browse/LOG4J2-2399?focusedWorklogId=848083&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848083 ] ASF GitHub Bot logged work on LOG4J2-2399: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2656) Add possibility to ignore exception if kafka connection error occurred

[ https://issues.apache.org/jira/browse/LOG4J2-2656?focusedWorklogId=848087&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848087 ] ASF GitHub Bot logged work on LOG4J2-2656: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2332) Unresolved variables in any file appender

[ https://issues.apache.org/jira/browse/LOG4J2-2332?focusedWorklogId=848082&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848082 ] ASF GitHub Bot logged work on LOG4J2-2332: -- Author: ASF GitHub

[jira] [Work logged] (LOG4J2-2750) Setting to disable extended stack trace for layouts

[ https://issues.apache.org/jira/browse/LOG4J2-2750?focusedWorklogId=848086&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848086 ] ASF GitHub Bot logged work on LOG4J2-2750: -- Author: ASF GitHub

[jira] [Closed] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-3650. --- Closing this due to info provider by the reporter. > Release 2.20.0 missing artifa

[jira] [Comment Edited] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693694#comment-17693694 ] Jon Wilmoth edited comment on LOG4J2-3650 at 2/26/23 8:2

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693694#comment-17693694 ] Jon Wilmoth commented on LOG4J2-3650: - Thank you [~rgoers].  We use

[jira] [Resolved] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3650. - Resolution: Information Provided > Release 2.20.0 missing artifa

[jira] [Comment Edited] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692254#comment-17692254 ] Ralph Goers edited comment on LOG4J2-3650 at 2/22/23 3:5

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692254#comment-17692254 ] Ralph Goers commented on LOG4J2-3650: - This is going to be a bit of a long an

[jira] [Comment Edited] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692049#comment-17692049 ] Piotr Karwasz edited comment on LOG4J2-3650 at 2/22/23 9:2

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692049#comment-17692049 ] Piotr Karwasz commented on LOG4J2-3650: --- [~jonwilm...@yahoo.com], Log4j2

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691999#comment-17691999 ] Volkan Yazici commented on LOG4J2-3650: --- Test JARs are not supposed t

[jira] [Created] (LOG4J2-3650) Release 2.20.0 missing artifacts

Jon Wilmoth created LOG4J2-3650: --- Summary: Release 2.20.0 missing artifacts Key: LOG4J2-3650 URL: https://issues.apache.org/jira/browse/LOG4J2-3650 Project: Log4j 2 Issue Type: Bug

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

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686726#comment-17686726 ] Gus Heck commented on LOG4J2-1990: -- Hmm this makes debugging custom appenders

[jira] [Updated] (LOG4J2-3642) Consider Osgi versions older than 1.5 as not available.

[ https://issues.apache.org/jira/browse/LOG4J2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3642: -- Priority: Minor (was: Major) > Consider Osgi versions older than 1.5 as not availa

[jira] [Updated] (LOG4J2-3642) Consider Osgi versions older than 1.5 as not available.

[ https://issues.apache.org/jira/browse/LOG4J2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3642: -- Fix Version/s: 2.20.0 > Consider Osgi versions older than 1.5 as not availa

[jira] [Resolved] (LOG4J2-3642) Consider Osgi versions older than 1.5 as not available.

[ https://issues.apache.org/jira/browse/LOG4J2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3642. --- Resolution: Fixed > Consider Osgi versions older than 1.5 as not availa

[jira] [Commented] (LOG4J2-3649) catching() is missing in KotlinLogger

[ https://issues.apache.org/jira/browse/LOG4J2-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686078#comment-17686078 ] Matt Sicker commented on LOG4J2-3649: - Oh nice catch before I got around to a 1

[jira] [Updated] (LOG4J2-3649) catching() is missing in KotlinLogger

[ https://issues.apache.org/jira/browse/LOG4J2-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-3649: Fix Version/s: Kotlin 1.3.0 > catching() is missing in KotlinLog

[jira] [Commented] (LOG4J2-3624) NoClassDefFoundError initializing PropertiesUtil in Servlet 2.5 container

[ https://issues.apache.org/jira/browse/LOG4J2-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685494#comment-17685494 ] Piotr Karwasz commented on LOG4J2-3624: --- [~nsush...@openfinance.com], I s

[jira] [Updated] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3621: -- Priority: Minor (was: Major) > Log4J 2.19 breaks contract of order of loading of Sys

[jira] [Resolved] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3621. --- Resolution: Fixed > Log4J 2.19 breaks contract of order of loading of System Propert

[jira] [Updated] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3621: -- Fix Version/s: 2.20.0 > Log4J 2.19 breaks contract of order of loading of System Propert

[jira] [Created] (LOG4J2-3649) catching() is missing in KotlinLogger

Björn Michael created LOG4J2-3649: - Summary: catching() is missing in KotlinLogger Key: LOG4J2-3649 URL: https://issues.apache.org/jira/browse/LOG4J2-3649 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685193#comment-17685193 ] Adwait Kumar Singh commented on LOG4J2-3621: [~pkarwasz], I went

[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3601: -- Fix Version/s: 2.20.0 > log4j-slf4j2: change of dependency scope for log4j-c

[jira] [Resolved] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3601. --- Resolution: Fixed > log4j-slf4j2: change of dependency scope for log4j-c

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