[jira] [Commented] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

[ https://issues.apache.org/jira/browse/LOG4J2-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895828#comment-13895828 ] Remko Popma commented on LOG4J2-531: Geoff, just a preliminary update (still

[jira] [Commented] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

[ https://issues.apache.org/jira/browse/LOG4J2-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895846#comment-13895846 ] Remko Popma commented on LOG4J2-531: Update: on my home laptop a rollover takes 5

[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: Reopening this after discussion on ML clarified that this is a feature request to support keeping

[jira] [Commented] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

[ https://issues.apache.org/jira/browse/LOG4J2-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895903#comment-13895903 ] Remko Popma commented on LOG4J2-531: Well, this is a nasty one... Sorry if what

[jira] [Resolved] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

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

[jira] [Commented] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

[ https://issues.apache.org/jira/browse/LOG4J2-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896026#comment-13896026 ] Remko Popma commented on LOG4J2-531: I will add JUnit tests for this ASAP. Probably

[jira] [Commented] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

[ https://issues.apache.org/jira/browse/LOG4J2-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896035#comment-13896035 ] Remko Popma commented on LOG4J2-531: Understood. I was also thinking to refactor the

[jira] [Commented] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

[ https://issues.apache.org/jira/browse/LOG4J2-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896038#comment-13896038 ] Remko Popma commented on LOG4J2-531: I just re-read your ML message realized your

[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=13896129#comment-13896129 ] Remko Popma commented on LOG4J2-520: Thanks Andre! I was able to reproduce this on my

[jira] [Commented] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

[ https://issues.apache.org/jira/browse/LOG4J2-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896139#comment-13896139 ] Remko Popma commented on LOG4J2-531: Geoff, the fix just made it into the 2.0-rc1

[jira] [Comment Edited] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

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

[jira] [Commented] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

[ https://issues.apache.org/jira/browse/LOG4J2-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896737#comment-13896737 ] Remko Popma commented on LOG4J2-531: Geoff, thanks first of all for confirming that

[jira] [Created] (LOG4J2-535) Rolled log files end up in the wrong directory

Remko Popma created LOG4J2-535: -- Summary: Rolled log files end up in the wrong directory Key: LOG4J2-535 URL: https://issues.apache.org/jira/browse/LOG4J2-535 Project: Log4j 2 Issue Type: Bug

[jira] [Closed] (LOG4J2-531) Rolled log files overwritten by RollingFile appender with composite time and size based policies

[ https://issues.apache.org/jira/browse/LOG4J2-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-531. -- Geoff, If you don't mind, I would like to close this issue (seeing that the title/description issue of

[jira] [Updated] (LOG4J2-535) Rolled log files end up in the wrong directory

[ https://issues.apache.org/jira/browse/LOG4J2-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-535: --- Description: Follow-up for issue LOG4J2-531: the main issue (rolled over archives were overwritten)

[jira] [Commented] (LOG4J2-536) Project Depencies page has no content

[ https://issues.apache.org/jira/browse/LOG4J2-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898807#comment-13898807 ] Remko Popma commented on LOG4J2-536: What should go on this page? The dependencies of

[jira] [Commented] (LOG4J2-443) log4j2 LoggerContext not showing up in JMX Gui or JConsole

[ https://issues.apache.org/jira/browse/LOG4J2-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13899110#comment-13899110 ] Remko Popma commented on LOG4J2-443: I saw a similar error when I was testing my fixes

[jira] [Comment Edited] (LOG4J2-443) log4j2 LoggerContext not showing up in JMX Gui or JConsole

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

[jira] [Commented] (LOG4J2-443) log4j2 LoggerContext not showing up in JMX Gui or JConsole

[ https://issues.apache.org/jira/browse/LOG4J2-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13900924#comment-13900924 ] Remko Popma commented on LOG4J2-443: Colin, thanks for verifying! It looks like you

[jira] [Updated] (LOG4J2-537) application does not end.

[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-537: --- Environment: program does not end. configuration {code} ?xml version=1.0 encoding=UTF-8?

[jira] [Updated] (LOG4J2-537) application does not end.

[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-537: --- Description: helloworld program does not end. was: helloworld program does not end.

[jira] [Updated] (LOG4J2-537) application does not end.

[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-537: --- Description: The helloworld program below does not end. (Process keeps running.) configuration:

[jira] [Updated] (LOG4J2-537) application does not end.

[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-537: --- Description: The helloworld program below does not end. (Process keeps running.) configuration:

[jira] [Assigned] (LOG4J2-539) IllegalArgumentException after editing config, pressing Reconfigure using XML below

[ https://issues.apache.org/jira/browse/LOG4J2-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-539: -- Assignee: Remko Popma IllegalArgumentException after editing config, pressing Reconfigure

[jira] [Assigned] (LOG4J2-538) occasional ArrayIndexOutOfBoundsException after pressing reconfigure with XML below

[ https://issues.apache.org/jira/browse/LOG4J2-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-538: -- Assignee: Remko Popma occasional ArrayIndexOutOfBoundsException after pressing reconfigure

[jira] [Commented] (LOG4J2-538) occasional ArrayIndexOutOfBoundsException after pressing reconfigure with XML below

[ https://issues.apache.org/jira/browse/LOG4J2-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13903176#comment-13903176 ] Remko Popma commented on LOG4J2-538: I've made a change (revision 1568957) to ensure

[jira] [Reopened] (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 reopened LOG4J2-345: Re-opening this issue as the fix seems incomplete/incorrect: the [OSGi bin archive for

[jira] [Commented] (LOG4J2-346) Cyclic dependency in OSGi-context. Apache Log4j SLF4J Binding - slf4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13903289#comment-13903289 ] Remko Popma commented on LOG4J2-346: Matt, I've committed your patch in revision , can

[jira] [Comment Edited] (LOG4J2-346) Cyclic dependency in OSGi-context. Apache Log4j SLF4J Binding - slf4j-api

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

[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=13903291#comment-13903291 ] Remko Popma commented on LOG4J2-373: Matt, you mentioned that what you have in mind

[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=13903823#comment-13903823 ] Remko Popma commented on LOG4J2-373: I see. Personally, if changes to log4j-core are

[jira] [Reopened] (LOG4J2-391) Flume appender crashes when lock timeout occurs

[ https://issues.apache.org/jira/browse/LOG4J2-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-391: Flume appender crashes when lock timeout occurs ---

[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: --- Affects Version/s: 2.0-rc1 I added rc1 to the affected versions. By the way, is the reason you're

[jira] [Commented] (LOG4J2-542) LogEvents with exceptions fail to deserialize

[ https://issues.apache.org/jira/browse/LOG4J2-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906328#comment-13906328 ] Remko Popma commented on LOG4J2-542: For background: the {{throwable}} field was added

[jira] [Commented] (LOG4J2-542) LogEvents with exceptions fail to deserialize

[ https://issues.apache.org/jira/browse/LOG4J2-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907957#comment-13907957 ] Remko Popma commented on LOG4J2-542: When consuming a serialized log event, what

[jira] [Commented] (LOG4J2-521) RollingRandomAccessFile + Async Appender skip logs sometimes (while logging into same file and while switching to another log file)

[ https://issues.apache.org/jira/browse/LOG4J2-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907965#comment-13907965 ] Remko Popma commented on LOG4J2-521: JavaTech, can you clarify how this issue

[jira] [Updated] (LOG4J2-493) Problem with AsyncLogger when web app is deployed/undeployed multiple times

[ https://issues.apache.org/jira/browse/LOG4J2-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-493: --- Description: When redeploying my application in tomcat multiple times, I get an exception:

[jira] [Commented] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909137#comment-13909137 ] Remko Popma commented on LOG4J2-505: Sorry, I don't understand your question about

[jira] [Commented] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909161#comment-13909161 ] Remko Popma commented on LOG4J2-505: About the Disruptor in general, I am not aware of

[jira] [Comment Edited] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

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

[jira] [Commented] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909203#comment-13909203 ] Remko Popma commented on LOG4J2-505: If you're interested in looking at the Disruptor

[jira] [Commented] (LOG4J2-537) application does not end.

[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915194#comment-13915194 ] Remko Popma commented on LOG4J2-537: The reason I asked is that I'm trying to

[jira] [Commented] (LOG4J2-554) No easy way to point to a configuration file in the WEB-INF folder

[ https://issues.apache.org/jira/browse/LOG4J2-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915855#comment-13915855 ] Remko Popma commented on LOG4J2-554: I know anything you put under WEB-INF/classes is

[jira] [Commented] (LOG4J2-554) No easy way to point to a configuration file in the WEB-INF folder

[ https://issues.apache.org/jira/browse/LOG4J2-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13916099#comment-13916099 ] Remko Popma commented on LOG4J2-554: {{log4jConfiguration}} is the old log4j-1.2

[jira] [Created] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

Remko Popma created LOG4J2-555: -- Summary: Location-based functionality broken in AbstractLoggerWrapper subclasses Key: LOG4J2-555 URL: https://issues.apache.org/jira/browse/LOG4J2-555 Project: Log4j 2

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

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917298#comment-13917298 ] Remko Popma commented on LOG4J2-519: vibin, the quick fix may be to use %c (lowercase)

[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=13917298#comment-13917298 ] Remko Popma edited comment on LOG4J2-519 at 3/2/14 6:25 AM:

[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=13917298#comment-13917298 ] Remko Popma edited comment on LOG4J2-519 at 3/2/14 6:26 AM:

[jira] [Comment Edited] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917313#comment-13917313 ] Remko Popma edited comment on LOG4J2-555 at 3/2/14 7:21 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: --- Attachment: (was: Generate.java) Custom/Extended Loggers ---

[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 Generate_old_20140130.java I've updated the attached

[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: Please try out the attached [^Generate.java] tool that provides the functionality

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917362#comment-13917362 ] Remko Popma commented on LOG4J2-555: With hindsight I probably saw the

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917419#comment-13917419 ] Remko Popma commented on LOG4J2-555: I keep thinking there must be a more robust way

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917569#comment-13917569 ] Remko Popma commented on LOG4J2-555: Hey Gary! I missed your comment. Yeah, I know!

[jira] [Commented] (LOG4J2-543) Add JDO database appender

[ https://issues.apache.org/jira/browse/LOG4J2-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917643#comment-13917643 ] Remko Popma commented on LOG4J2-543: Just FYI, usually I would prefer to leave the

[jira] [Commented] (LOG4J2-346) Cyclic dependency in OSGi-context. Apache Log4j SLF4J Binding - slf4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917652#comment-13917652 ] Remko Popma commented on LOG4J2-346: It's probably best to aim to match OSGi users

[jira] [Commented] (LOG4J2-543) Add JDO database appender

[ https://issues.apache.org/jira/browse/LOG4J2-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917653#comment-13917653 ] Remko Popma commented on LOG4J2-543: Unless adding something would somehow break

[jira] [Commented] (LOG4J2-547) Update LoggerStream API

[ https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917734#comment-13917734 ] Remko Popma commented on LOG4J2-547: If you need AbstractLogger functionality that is

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918962#comment-13918962 ] Remko Popma commented on LOG4J2-555: I do have a refactoring in mind that would

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

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923148#comment-13923148 ] Remko Popma commented on LOG4J2-519: Bruce, it looks like the FQCN is declared, but

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923194#comment-13923194 ] Remko Popma commented on LOG4J2-555: I won't have time to work out the details for

[jira] [Comment Edited] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923194#comment-13923194 ] Remko Popma edited comment on LOG4J2-555 at 3/7/14 1:09 AM: I

[jira] [Commented] (LOG4J2-562) Improve ability to create custom extended logger

[ https://issues.apache.org/jira/browse/LOG4J2-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924804#comment-13924804 ] Remko Popma commented on LOG4J2-562: I had a look at the attached patch. It looks like

[jira] [Updated] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-555: --- Attachment: LOG4J2-555-delegate.patch Inspired by Gary's call for a refactoring, please find

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925106#comment-13925106 ] Remko Popma commented on LOG4J2-555: I completely agree that if there is any

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925138#comment-13925138 ] Remko Popma commented on LOG4J2-555: I did some performance tests but did not see any

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925346#comment-13925346 ] Remko Popma commented on LOG4J2-555: Hotspot compiles to native code if the method is

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925443#comment-13925443 ] Remko Popma commented on LOG4J2-555: The enums (like MsgBuilder) use the

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932812#comment-13932812 ] Remko Popma commented on LOG4J2-555: At first glance this accomplishes the same as

[jira] [Commented] (LOG4J2-565) Log4j2 loading time

[ https://issues.apache.org/jira/browse/LOG4J2-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932825#comment-13932825 ] Remko Popma commented on LOG4J2-565: In your configuration, can you change the first

[jira] [Commented] (LOG4J2-565) Log4j2 loading time

[ https://issues.apache.org/jira/browse/LOG4J2-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933144#comment-13933144 ] Remko Popma commented on LOG4J2-565: It looks like you unzipped the log4j api and core

[jira] [Created] (LOG4J2-566) Configure RollingRandomAccessFileAppender buffer size

Remko Popma created LOG4J2-566: -- Summary: Configure RollingRandomAccessFileAppender buffer size Key: LOG4J2-566 URL: https://issues.apache.org/jira/browse/LOG4J2-566 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-402) Configure RandomAccessFileAppender buffer size

[ https://issues.apache.org/jira/browse/LOG4J2-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933152#comment-13933152 ] Remko Popma commented on LOG4J2-402: Good catch! I've created LOG4J2-566 for this.

[jira] [Commented] (LOG4J2-566) Configure RollingRandomAccessFileAppender buffer size

[ https://issues.apache.org/jira/browse/LOG4J2-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1392#comment-1392 ] Remko Popma commented on LOG4J2-566: Oh wow, that is fast! Would it be possible for

[jira] [Commented] (LOG4J2-565) Log4j2 loading time

[ https://issues.apache.org/jira/browse/LOG4J2-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933376#comment-13933376 ] Remko Popma commented on LOG4J2-565: Looks like my analysis was incorrect or

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

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13935960#comment-13935960 ] Remko Popma commented on LOG4J2-519: This weekend I won't have time (one more push for

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13935983#comment-13935983 ] Remko Popma commented on LOG4J2-555: Thanks for the overview. It is helpful to not

[jira] [Reopened] (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 reopened LOG4J2-323: Assignee: (was: Nick Williams) Re-opened for investigation. ThreadLocal-leak on tomcat

[jira] [Commented] (LOG4J2-571) AsyncLoggerConfig-1 Thread consuming excessive CPU

[ https://issues.apache.org/jira/browse/LOG4J2-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13940200#comment-13940200 ] Remko Popma commented on LOG4J2-571: Can you create another thread dump after setting

[jira] [Commented] (LOG4J2-571) AsyncLoggerConfig-1 Thread consuming excessive CPU

[ https://issues.apache.org/jira/browse/LOG4J2-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13940352#comment-13940352 ] Remko Popma commented on LOG4J2-571: I'm glad the problem is resolved. I also don't

[jira] [Closed] (LOG4J2-571) AsyncLoggerConfig-1 Thread consuming excessive CPU

[ https://issues.apache.org/jira/browse/LOG4J2-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-571. -- Resolution: Not A Problem Closing this issue. AsyncLoggerConfig-1 Thread consuming excessive CPU

[jira] [Comment Edited] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943949#comment-13943949 ] Remko Popma edited comment on LOG4J2-555 at 3/22/14 1:57 PM: -

[jira] [Comment Edited] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943949#comment-13943949 ] Remko Popma edited comment on LOG4J2-555 at 3/22/14 2:25 PM: -

[jira] [Commented] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944095#comment-13944095 ] Remko Popma commented on LOG4J2-555: Gary, looks like our messages crossed. :-) I

[jira] [Commented] (LOG4J2-547) Update LoggerStream API

[ https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944313#comment-13944313 ] Remko Popma commented on LOG4J2-547: Interesting. This looks like a problem in the

[jira] [Commented] (LOG4J2-547) Update LoggerStream API

[ https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944333#comment-13944333 ] Remko Popma commented on LOG4J2-547: FYI, this logic lives in

[jira] [Resolved] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

[ https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-555. Resolution: Fixed Fixed in revision 1580445, based on log4j2-555-bbrouwer-2.patch with Gary's

[jira] [Comment Edited] (LOG4J2-555) Location-based functionality broken in AbstractLoggerWrapper subclasses

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

[jira] [Created] (LOG4J2-574) Make Blocking the default WaitStrategy for Async Loggers

Remko Popma created LOG4J2-574: -- Summary: Make Blocking the default WaitStrategy for Async Loggers Key: LOG4J2-574 URL: https://issues.apache.org/jira/browse/LOG4J2-574 Project: Log4j 2 Issue

[jira] [Resolved] (LOG4J2-574) Make Blocking the default WaitStrategy for Async Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-574. Resolution: Fixed Fixed in revision 1580474. Make Blocking the default WaitStrategy for Async

[jira] [Closed] (LOG4J2-574) Make Blocking the default WaitStrategy for Async Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-574. -- Make Blocking the default WaitStrategy for Async Loggers

[jira] [Commented] (LOG4J2-571) AsyncLoggerConfig-1 Thread consuming excessive CPU

[ https://issues.apache.org/jira/browse/LOG4J2-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944383#comment-13944383 ] Remko Popma commented on LOG4J2-571: Raised LOG4J2-574 for the new default. This is

[jira] [Commented] (LOG4J2-537) application does not end.

[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944394#comment-13944394 ] Remko Popma commented on LOG4J2-537: Gleb, Sorry for the late response. You seem to

[jira] [Commented] (LOG4J2-570) Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944601#comment-13944601 ] Remko Popma commented on LOG4J2-570: I haven't looked at the code, but would it be

[jira] [Comment Edited] (LOG4J2-570) Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944601#comment-13944601 ] Remko Popma edited comment on LOG4J2-570 at 3/23/14 10:06 PM: --

[jira] [Comment Edited] (LOG4J2-575) Log4J2 and Tomee Plus 7.0.47 not working

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

[jira] [Commented] (LOG4J2-575) Log4J2 and Tomee Plus 7.0.47 not working

[ https://issues.apache.org/jira/browse/LOG4J2-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944652#comment-13944652 ] Remko Popma commented on LOG4J2-575: Alex, in your stackoverflow comments you

[jira] [Commented] (LOG4J2-547) Update LoggerStream API

[ https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944679#comment-13944679 ] Remko Popma commented on LOG4J2-547: Micro-benchmarks can be tricky stuff. Do you get

[jira] [Comment Edited] (LOG4J2-576) Add org.apache.logging.log4j.Logger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944718#comment-13944718 ] Remko Popma edited comment on LOG4J2-576 at 3/24/14 3:43 AM: -

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