[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=17084211#comment-17084211 ] Ralph Goers commented on LOG4J2-2820: - Log4j 2 will dynamically update its logging c

[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=17084210#comment-17084210 ] Matt Sicker commented on LOG4J2-2820: - Another approach could be to use the JConsole

[jira] [Reopened] (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:all-tabpanel ] Ralph Goers reopened LOG4J2-2820: - > updating the log4j configuration (log4j.properties) dynamically at runtime >

[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=17084206#comment-17084206 ] Ananda Reddy C commented on LOG4J2-2820: my apologizes,  we have already planned

[jira] [Closed] (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:all-tabpanel ] Ralph Goers closed LOG4J2-2820. --- Resolution: Invalid Closing since this is not for Logj4 2. > updating the log4j configuration (log4

[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=17084201#comment-17084201 ] Ralph Goers commented on LOG4J2-2820: - I really can't. The developers working on Log

[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=17084194#comment-17084194 ] Ananda Reddy C commented on LOG4J2-2820: thank you for update, could you pls upd

[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=17084192#comment-17084192 ] Ralph Goers commented on LOG4J2-2820: - I apologize. I missed that you stated you wer

[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-614097241 > I will keep this patch on my internal project for the moment, try to implement the visibility macros for GCC in the project and test i

[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-613915308 > I will keep this patch on my internal project for the moment, try to implement the visibility macros for GCC in the project a

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

aallrd commented on issue #22: Only exporting the log4cxx symbols by default URL: https://github.com/apache/logging-log4cxx/pull/22#issuecomment-613895179 Hello, Thank you for your comments, and for the interesting [GCC bugzilla report](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36022)