[jira] [Commented] (LOG4J2-2820) updating the log4j configuration (log4j.properties) dynamically at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083795#comment-17083795 ] Ananda Reddy C commented on LOG4J2-2820: Hi Ralph Thank you for quick turn arou

[GitHub] [logging-log4cxx] rm5248 commented on issue #22: Only exporting the log4cxx symbols by default

rm5248 commented on issue #22: Only exporting the log4cxx symbols by default URL: https://github.com/apache/logging-log4cxx/pull/22#issuecomment-613730871 > OTOH, the changed implementation of CMAKE doesn't look too invasive and can easily be disabled if it makes problems in future by all u

Jenkins job log4j/master#51 back to normal

The build for log4j/master completed successfully and is back to normal. Build: https://builds.apache.org/job/log4j/job/master/51/ Logs: https://builds.apache.org/job/log4j/job/master/51/console Changes: https://builds.apache.org/job/log4j/job/master/51/changes -- Mr. Jenkins Director of Continu

Jenkins job log4j/master#50 failed

There is a build failure in log4j/master. Build: https://builds.apache.org/job/log4j/job/master/50/ Logs: https://builds.apache.org/job/log4j/job/master/50/console Changes: https://builds.apache.org/job/log4j/job/master/50/changes -- Mr. Jenkins Director of Continuous Integration

Jenkins job log4j/master#49 failed

There is a build failure in log4j/master. Build: https://builds.apache.org/job/log4j/job/master/49/ Logs: https://builds.apache.org/job/log4j/job/master/49/console Changes: https://builds.apache.org/job/log4j/job/master/49/changes -- Mr. Jenkins Director of Continuous Integration

[jira] [Commented] (LOG4J2-2820) updating the log4j configuration (log4j.properties) dynamically at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083369#comment-17083369 ] Ralph Goers commented on LOG4J2-2820: - Please see [http://logging.apache.org/log4j/2

[jira] [Work logged] (LOG4J2-2391) Investigate ThrowableProxy performance

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

[GitHub] [logging-log4j2] carterkozak commented on issue #210: [LOG4J2-2391] Lazily initialize ThrowableProxy data

carterkozak commented on issue #210: [LOG4J2-2391] Lazily initialize ThrowableProxy data URL: https://github.com/apache/logging-log4j2/pull/210#issuecomment-613486202 Sorry, this has gotten stale and I need to come back to the problem when I have some time. I'm not confident this is the be

[jira] [Created] (LOG4J2-2820) updating the log4j configuration (log4j.properties) dynamically at runtime

Ananda Reddy C created LOG4J2-2820: -- Summary: updating the log4j configuration (log4j.properties) dynamically at runtime Key: LOG4J2-2820 URL: https://issues.apache.org/jira/browse/LOG4J2-2820 Proje

[jira] [Commented] (LOG4J2-2391) Investigate ThrowableProxy performance

[ https://issues.apache.org/jira/browse/LOG4J2-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083151#comment-17083151 ] Guoqiang Jiang commented on LOG4J2-2391: Is this ready now?[~ckozak] > Investig

[jira] [Comment Edited] (LOG4J2-2696) Class loading for extended stack traces causes performance issues

[ https://issues.apache.org/jira/browse/LOG4J2-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083133#comment-17083133 ] Joe Jordan edited comment on LOG4J2-2696 at 4/14/20, 11:50 AM: ---

[jira] [Commented] (LOG4J2-2696) Class loading for extended stack traces causes performance issues

[ https://issues.apache.org/jira/browse/LOG4J2-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083133#comment-17083133 ] Joe Jordan commented on LOG4J2-2696: I worked around the issue by disabling extended

[jira] [Comment Edited] (LOG4J2-2696) Class loading for extended stack traces causes performance issues

[ https://issues.apache.org/jira/browse/LOG4J2-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083133#comment-17083133 ] Joe Jordan edited comment on LOG4J2-2696 at 4/14/20, 11:49 AM: ---

[jira] [Commented] (LOG4J2-2696) Class loading for extended stack traces causes performance issues

[ https://issues.apache.org/jira/browse/LOG4J2-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083130#comment-17083130 ] Guoqiang Jiang commented on LOG4J2-2696: +1. Any plan here? > Class loading for

[GitHub] [logging-log4cxx] ams-tschoening commented on issue #22: Only exporting the log4cxx symbols by default

ams-tschoening commented on issue #22: Only exporting the log4cxx symbols by default URL: https://github.com/apache/logging-log4cxx/pull/22#issuecomment-613274847 So what's the strategy then? @aallrd Do you want to give the approach of @rm5248 a try and see if it fixes your concrete proble