[jira] [Assigned] (LOG4J2-392) Intermittent errors with appenders

[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-392: -- Assignee: Remko Popma Intermittent errors with appenders --

[jira] [Commented] (LOG4J2-518) Logging of nested list uses incorrect charset

[ https://issues.apache.org/jira/browse/LOG4J2-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13883987#comment-13883987 ] Remko Popma commented on LOG4J2-518: I cannot reproduce the problem with this code:

[jira] [Created] (LOG4J2-519) Custom/Extended Loggers

Remko Popma created LOG4J2-519: -- Summary: Custom/Extended Loggers Key: LOG4J2-519 URL: https://issues.apache.org/jira/browse/LOG4J2-519 Project: Log4j 2 Issue Type: New Feature

[jira] [Commented] (LOG4J2-518) Logging of nested list uses incorrect charset

[ https://issues.apache.org/jira/browse/LOG4J2-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884102#comment-13884102 ] Remko Popma commented on LOG4J2-518: Yes, I don't understand how logging a list of

[jira] [Assigned] (LOG4J2-520) RollingRandomAccessFile with Async Appender skip logs

[ https://issues.apache.org/jira/browse/LOG4J2-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-520: -- Assignee: Remko Popma RollingRandomAccessFile with Async Appender skip logs

[jira] [Updated] (LOG4J2-520) RollingRandomAccessFile with Async Appender skip logs

[ https://issues.apache.org/jira/browse/LOG4J2-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-520: --- Description: I have written a sample code which will write DEBUG, INFO , WARN logs in a single

[jira] [Updated] (LOG4J2-520) RollingRandomAccessFile with Async Appender skip logs

[ https://issues.apache.org/jira/browse/LOG4J2-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-520: --- Description: I have written a sample code which will write DEBUG, INFO , WARN logs in a single

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Attachment: Generate.java Attached a first attempt at a source code generator (Generate.java).

[jira] [Commented] (LOG4J2-518) Logging of nested list uses incorrect charset

[ https://issues.apache.org/jira/browse/LOG4J2-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884322#comment-13884322 ] Remko Popma commented on LOG4J2-518: Thanks! I can now also reproduce the problem.

[jira] [Commented] (LOG4J2-492) MalformedObjectNameException: Invalid escape sequence... under Jetty

[ https://issues.apache.org/jira/browse/LOG4J2-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885167#comment-13885167 ] Remko Popma commented on LOG4J2-492: I reopened this yesterday afternoon as I still

[jira] [Comment Edited] (LOG4J2-492) MalformedObjectNameException: Invalid escape sequence... under Jetty

[ https://issues.apache.org/jira/browse/LOG4J2-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885167#comment-13885167 ] Remko Popma edited comment on LOG4J2-492 at 1/29/14 9:43 AM: -

[jira] [Resolved] (LOG4J2-492) MalformedObjectNameException: Invalid escape sequence... under Jetty

[ https://issues.apache.org/jira/browse/LOG4J2-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-492. Resolution: Fixed I've made a change to escape the context name before unregistering the

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Attachment: Generate.java Updated attached file Generate.java with code change for the renamed

[jira] [Comment Edited] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884294#comment-13884294 ] Remko Popma edited comment on LOG4J2-519 at 1/30/14 12:55 AM: --

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Description: *[#Extending] the Logger interface* LOG4J2-41 added support for custom log Levels.

[jira] [Comment Edited] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886105#comment-13886105 ] Remko Popma edited comment on LOG4J2-519 at 1/30/14 12:56 AM: --

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Description: {anchor:Extending} *[#Extending] the Logger interface* LOG4J2-41 added support for

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Description: {anchor:Extending} *[#Extending] the Logger interface* LOG4J2-41 added support for

[jira] [Commented] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886239#comment-13886239 ] Remko Popma commented on LOG4J2-323: Nick, nice catch! Thanks! Mickael, can you

[jira] [Commented] (LOG4J2-522) Split Logger interface in two with named level methods (info, warn, ...) in the subinterface.

[ https://issues.apache.org/jira/browse/LOG4J2-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886345#comment-13886345 ] Remko Popma commented on LOG4J2-522: +1: we probably want to do this before 2.0 GA.

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Description: {anchor:Extending} *[#Extending] the Logger interface* LOG4J2-41 added support for

[jira] [Commented] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887064#comment-13887064 ] Remko Popma commented on LOG4J2-323: Trunk built ok for me just now. Do you still have

[jira] [Comment Edited] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887064#comment-13887064 ] Remko Popma edited comment on LOG4J2-323 at 1/31/14 12:24 AM: --

[jira] [Updated] (LOG4J2-385) Unable to roll log files monthly

[ https://issues.apache.org/jira/browse/LOG4J2-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-385: --- Description: Attempting to use FastRollingFile appender and configure log file rollover to occur

[jira] [Commented] (LOG4J2-385) Unable to roll log files monthly

[ https://issues.apache.org/jira/browse/LOG4J2-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887396#comment-13887396 ] Remko Popma commented on LOG4J2-385: Team, what is the spec for rollover? * Starting

[jira] [Comment Edited] (LOG4J2-385) Unable to roll log files monthly

[ https://issues.apache.org/jira/browse/LOG4J2-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887396#comment-13887396 ] Remko Popma edited comment on LOG4J2-385 at 1/31/14 2:44 AM: -

[jira] [Commented] (LOG4J2-385) Unable to roll log files monthly

[ https://issues.apache.org/jira/browse/LOG4J2-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887434#comment-13887434 ] Remko Popma commented on LOG4J2-385: What do Log4j-1.2 and Logback do in the above

[jira] [Comment Edited] (LOG4J2-385) Unable to roll log files monthly

[ https://issues.apache.org/jira/browse/LOG4J2-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887434#comment-13887434 ] Remko Popma edited comment on LOG4J2-385 at 1/31/14 4:02 AM: -

[jira] [Comment Edited] (LOG4J2-385) Unable to roll log files monthly

[ https://issues.apache.org/jira/browse/LOG4J2-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887434#comment-13887434 ] Remko Popma edited comment on LOG4J2-385 at 1/31/14 4:21 AM: -

[jira] [Commented] (LOG4J2-385) Unable to roll log files monthly

[ https://issues.apache.org/jira/browse/LOG4J2-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887467#comment-13887467 ] Remko Popma commented on LOG4J2-385: Cron... to be honest, I know it is a standard,

[jira] [Commented] (LOG4J2-385) Unable to roll log files monthly

[ https://issues.apache.org/jira/browse/LOG4J2-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887524#comment-13887524 ] Remko Popma commented on LOG4J2-385: After checking the behaviour of Log4J-1.2 and

[jira] [Commented] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887578#comment-13887578 ] Remko Popma commented on LOG4J2-323: Ah, I see it now... That method actually has a

[jira] [Commented] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887681#comment-13887681 ] Remko Popma commented on LOG4J2-323: Removed the @Override to fix the compilation

[jira] [Closed] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-323. -- Closing this issue. ThreadLocal-leak on tomcat shutdown when using async logging

[jira] [Resolved] (LOG4J2-385) Unable to roll log files monthly

[ https://issues.apache.org/jira/browse/LOG4J2-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-385. Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed the above issues with monthly, weekly,

[jira] [Commented] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887758#comment-13887758 ] Remko Popma commented on LOG4J2-323: No problem! :-) ThreadLocal-leak on tomcat

[jira] [Commented] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887867#comment-13887867 ] Remko Popma commented on LOG4J2-500: This is not as straight-forward as I thought: it

[jira] [Created] (LOG4J2-524) Rollover does not delete older archives

Remko Popma created LOG4J2-524: -- Summary: Rollover does not delete older archives Key: LOG4J2-524 URL: https://issues.apache.org/jira/browse/LOG4J2-524 Project: Log4j 2 Issue Type: Bug

[jira] [Updated] (LOG4J2-524) Rollover does not delete older archives

[ https://issues.apache.org/jira/browse/LOG4J2-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-524: --- Description: This issue was raised by Kireet on the log4j-user mailing list: I am trying to use the

[jira] [Updated] (LOG4J2-524) Rollover does not delete older rolled over files

[ https://issues.apache.org/jira/browse/LOG4J2-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-524: --- Fix Version/s: 2.0-beta9 Summary: Rollover does not delete older rolled over files (was:

[jira] [Commented] (LOG4J2-524) Rollover does not delete older archives

[ https://issues.apache.org/jira/browse/LOG4J2-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13888459#comment-13888459 ] Remko Popma commented on LOG4J2-524: I thought this might be a bug but it seems like

[jira] [Closed] (LOG4J2-524) Rollover does not delete older rolled over files

[ https://issues.apache.org/jira/browse/LOG4J2-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-524. -- Rollover does not delete older rolled over files

[jira] [Comment Edited] (LOG4J2-524) Rollover does not delete older rolled over files

[ https://issues.apache.org/jira/browse/LOG4J2-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13888459#comment-13888459 ] Remko Popma edited comment on LOG4J2-524 at 2/1/14 5:15 AM: I

[jira] [Reopened] (LOG4J2-524) Rollover does not delete older rolled over files

[ https://issues.apache.org/jira/browse/LOG4J2-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-524: Rollover does not delete older rolled over files

[jira] [Resolved] (LOG4J2-524) Rollover does not delete older rolled over files

[ https://issues.apache.org/jira/browse/LOG4J2-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-524. Resolution: Not A Problem I'm closing this issue as not a problem. Please feel free to re-open if

[jira] [Created] (LOG4J2-525) Broken link to RoutingAppender at bottom of PropertySubstitution section on Config page

Remko Popma created LOG4J2-525: -- Summary: Broken link to RoutingAppender at bottom of PropertySubstitution section on Config page Key: LOG4J2-525 URL: https://issues.apache.org/jira/browse/LOG4J2-525

[jira] [Closed] (LOG4J2-525) Broken link to RoutingAppender at bottom of PropertySubstitution section on Config page

[ https://issues.apache.org/jira/browse/LOG4J2-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-525. -- Broken link to RoutingAppender at bottom of PropertySubstitution section on Config page

[jira] [Resolved] (LOG4J2-525) Broken link to RoutingAppender at bottom of PropertySubstitution section on Config page

[ https://issues.apache.org/jira/browse/LOG4J2-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-525. Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed in revision 1563732. Broken link to

[jira] [Commented] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889525#comment-13889525 ] Remko Popma commented on LOG4J2-500: This is still in progress, but I've made the

[jira] [Commented] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889543#comment-13889543 ] Remko Popma commented on LOG4J2-345: Can we safely apply this patch now, or would it

[jira] [Updated] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-345: --- Attachment: log4j2-345-patch-issue.png Matt, I have trouble applying the patch. Please see attached

[jira] [Commented] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890382#comment-13890382 ] Remko Popma commented on LOG4J2-345: The new patch seems to have the same issue. I'm

[jira] [Commented] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890595#comment-13890595 ] Remko Popma commented on LOG4J2-345: I see. Looks interesting. I'm using Subclipse

[jira] [Comment Edited] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890595#comment-13890595 ] Remko Popma edited comment on LOG4J2-345 at 2/4/14 11:57 AM: -

[jira] [Resolved] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-345. Resolution: Fixed Thanks Gary. I actually tried that before but gave up when I still got a red

[jira] [Commented] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890673#comment-13890673 ] Remko Popma commented on LOG4J2-345: One more thing about naming: I noticed that the

[jira] [Comment Edited] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890673#comment-13890673 ] Remko Popma edited comment on LOG4J2-345 at 2/4/14 1:44 PM:

[jira] [Commented] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891404#comment-13891404 ] Remko Popma commented on LOG4J2-519: *How to use the Generate tool* Please follow the

[jira] [Commented] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891591#comment-13891591 ] Remko Popma commented on LOG4J2-345: Ah! Oops. Good point. The log4j-1.2-api is _not_

[jira] [Commented] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891607#comment-13891607 ] Remko Popma commented on LOG4J2-345: They are all submodules of the log4j-osgi module.

[jira] [Comment Edited] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891607#comment-13891607 ] Remko Popma edited comment on LOG4J2-345 at 2/5/14 2:10 AM:

[jira] [Commented] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891678#comment-13891678 ] Remko Popma commented on LOG4J2-519: Bruce, there is still discussion going on on the

[jira] [Commented] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891687#comment-13891687 ] Remko Popma commented on LOG4J2-519: Gary, I agree, naming the factory method

[jira] [Comment Edited] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891687#comment-13891687 ] Remko Popma edited comment on LOG4J2-519 at 2/5/14 4:13 AM:

[jira] [Commented] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891975#comment-13891975 ] Remko Popma commented on LOG4J2-500: I may need some help with this... With the

[jira] [Comment Edited] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891975#comment-13891975 ] Remko Popma edited comment on LOG4J2-500 at 2/5/14 10:34 AM: -

[jira] [Commented] (LOG4J2-511) Referenced appenders on async appender are shutdown prematurely

[ https://issues.apache.org/jira/browse/LOG4J2-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892814#comment-13892814 ] Remko Popma commented on LOG4J2-511: I haven't looked at this in detail yet but I

[jira] [Commented] (LOG4J2-493) NPE in AsyncLogger.shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892821#comment-13892821 ] Remko Popma commented on LOG4J2-493: They are not related: LOG4J2-511 is about the

[jira] [Commented] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893026#comment-13893026 ] Remko Popma commented on LOG4J2-519: Bruce, interesting point, I hadn't thought of

[jira] [Commented] (LOG4J2-373) Classloader issue in OSGi-environment

[ https://issues.apache.org/jira/browse/LOG4J2-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893107#comment-13893107 ] Remko Popma commented on LOG4J2-373: Norval, it may be a good idea to raise the

[jira] [Comment Edited] (LOG4J2-373) Classloader issue in OSGi-environment

[ https://issues.apache.org/jira/browse/LOG4J2-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893107#comment-13893107 ] Remko Popma edited comment on LOG4J2-373 at 2/6/14 6:56 AM:

[jira] [Commented] (LOG4J2-511) Referenced appenders on async appender are shutdown prematurely

[ https://issues.apache.org/jira/browse/LOG4J2-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893352#comment-13893352 ] Remko Popma commented on LOG4J2-511: Andre, I agree that this issue and LOG4J2-392 may

[jira] [Resolved] (LOG4J2-511) Referenced appenders on async appender are shutdown prematurely

[ https://issues.apache.org/jira/browse/LOG4J2-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-511. Resolution: Fixed Fix Version/s: 2.0-rc1 I've made the above-mentioned change to

[jira] [Resolved] (LOG4J2-392) Intermittent errors with appenders

[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-392. Resolution: Fixed Fix Version/s: 2.0-rc1 I modified {{BaseConfiguration.stop()}} to ensure

[jira] [Commented] (LOG4J2-493) NPE in AsyncLogger.shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893372#comment-13893372 ] Remko Popma commented on LOG4J2-493: In revision 1565254 I made a change to

[jira] [Commented] (LOG4J2-392) Intermittent errors with appenders

[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894024#comment-13894024 ] Remko Popma commented on LOG4J2-392: Andre, thanks for checking! I think that you have

[jira] [Commented] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894189#comment-13894189 ] Remko Popma commented on LOG4J2-529: Nick, I tried deploying in Tomcat 8.0.1 but I get

[jira] [Created] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

Remko Popma created LOG4J2-529: -- Summary: Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy Key: LOG4J2-529 URL: https://issues.apache.org/jira/browse/LOG4J2-529 Project:

[jira] [Comment Edited] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894189#comment-13894189 ] Remko Popma edited comment on LOG4J2-529 at 2/7/14 4:35 AM:

[jira] [Commented] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894151#comment-13894151 ] Remko Popma commented on LOG4J2-500: The new ObjectNames correctly separate MBeans for

[jira] [Updated] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-529: --- Description: The log4j2 manuals

[jira] [Updated] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-529: --- Description: The log4j2 manuals

[jira] [Created] (LOG4J2-530) JMX Client GUI should dynamically update when LoggerContext MBeans are registered/unregistered in MBean server

Remko Popma created LOG4J2-530: -- Summary: JMX Client GUI should dynamically update when LoggerContext MBeans are registered/unregistered in MBean server Key: LOG4J2-530 URL:

[jira] [Comment Edited] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894151#comment-13894151 ] Remko Popma edited comment on LOG4J2-500 at 2/7/14 9:11 AM:

[jira] [Updated] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-529: --- Attachment: webapp2.war webapp1.war I've attached two webapps (webapp1.war and

[jira] [Comment Edited] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894570#comment-13894570 ] Remko Popma edited comment on LOG4J2-529 at 2/7/14 2:49 PM:

[jira] [Resolved] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-500. Resolution: Fixed Fix Version/s: 2.0-rc1 Unloading one webapp unloads JMX MBeans for all

[jira] [Closed] (LOG4J2-500) Unloading one webapp unloads JMX MBeans for all webapps

[ https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-500. -- Unloading one webapp unloads JMX MBeans for all webapps

[jira] [Commented] (LOG4J2-511) Referenced appenders on async appender are shutdown prematurely

[ https://issues.apache.org/jira/browse/LOG4J2-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894638#comment-13894638 ] Remko Popma commented on LOG4J2-511: James, if you verified that this solution works

[jira] [Updated] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-529: --- Attachment: (was: webapp1.war) Log4j2 does not auto-initialize on webapp deploy or

[jira] [Updated] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-529: --- Attachment: webapp1.war Nick, that is a good point. I tested again after updating web.xml with the

[jira] [Resolved] (LOG4J2-530) JMX Client GUI should dynamically update when LoggerContext MBeans are registered/unregistered in MBean server

[ https://issues.apache.org/jira/browse/LOG4J2-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-530. Resolution: Fixed Fix Version/s: 2.0-rc1 Fixed in revision 1565741. JMX Client GUI should

[jira] [Closed] (LOG4J2-530) JMX Client GUI should dynamically update when LoggerContext MBeans are registered/unregistered in MBean server

[ https://issues.apache.org/jira/browse/LOG4J2-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-530. -- JMX Client GUI should dynamically update when LoggerContext MBeans are registered/unregistered in MBean

[jira] [Comment Edited] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894667#comment-13894667 ] Remko Popma edited comment on LOG4J2-529 at 2/7/14 5:53 PM:

[jira] [Updated] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-529: --- Attachment: (was: webapp1.war) Log4j2 does not auto-initialize on webapp deploy or

[jira] [Updated] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-529: --- Attachment: webapp30-listener.war webapp30.war Log4j2 does not auto-initialize on

[jira] [Commented] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894877#comment-13894877 ] Remko Popma commented on LOG4J2-529: Very strange... I'll try again tomorrow with

[jira] [Closed] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-529. -- Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[jira] [Resolved] (LOG4J2-529) Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on undeploy

[ https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-529. Resolution: Not A Problem Fix Version/s: 2.0-rc1 I've confirmed that in Tomcat 7.0.50, the

[jira] [Commented] (LOG4J2-520) RollingRandomAccessFile with Async Appender skip logs

[ https://issues.apache.org/jira/browse/LOG4J2-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895504#comment-13895504 ] Remko Popma commented on LOG4J2-520: I tried but was unable to reproduce the issue

<    3   4   5   6   7   8   9   10   11   12   >