[jira] [Comment Edited] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293343#comment-17293343 ] Ralph Goers edited comment on LOG4J2-3035 at 3/2/21, 4:55 AM:

[jira] [Comment Edited] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293344#comment-17293344 ] Ralph Goers edited comment on LOG4J2-3035 at 3/2/21, 4:45 AM:

[jira] [Commented] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293344#comment-17293344 ] Ralph Goers commented on LOG4J2-3035: - I should also note that since it is impossibl

[jira] [Commented] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293343#comment-17293343 ] Ralph Goers commented on LOG4J2-3035: - If you are interested in contributing a few p

[jira] [Commented] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293325#comment-17293325 ] Carter Kozak commented on LOG4J2-3035: -- You can fork the repository on GitHub and c

[jira] [Commented] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293322#comment-17293322 ] Nishit k Ghosh commented on LOG4J2-3035: I do have a solution to this problem. C

[jira] [Comment Edited] (LOG4J2-3034) Change Log format based on currently active level

[ https://issues.apache.org/jira/browse/LOG4J2-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293321#comment-17293321 ] Ralph Goers edited comment on LOG4J2-3034 at 3/2/21, 3:23 AM:

[jira] [Commented] (LOG4J2-3034) Change Log format based on currently active level

[ https://issues.apache.org/jira/browse/LOG4J2-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293321#comment-17293321 ] Ralph Goers commented on LOG4J2-3034: - The issue description stated "If it is debug

[jira] [Commented] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293320#comment-17293320 ] Nishit k Ghosh commented on LOG4J2-3035: The log file is being deleted by a demo

[jira] [Closed] (LOG4J2-3032) Memory appender that can be flushed to another appender later

[ https://issues.apache.org/jira/browse/LOG4J2-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-3032. --- Resolution: Duplicate Closing as a duplicate > Memory appender that can be flushed to another appen

[jira] [Commented] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293316#comment-17293316 ] Ralph Goers commented on LOG4J2-3035: - Don't delete the file from an external proces

[jira] [Updated] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishit k Ghosh updated LOG4J2-3035: --- Summary: Refresh the Stale reference of Log File once the physical file is deleted by extern

[jira] [Created] (LOG4J2-3035) Refresh the Phantom reference of Log File once the physical file is deleted by external process

Nishit k Ghosh created LOG4J2-3035: -- Summary: Refresh the Phantom reference of Log File once the physical file is deleted by external process Key: LOG4J2-3035 URL: https://issues.apache.org/jira/browse/LOG4J2-303

[jira] [Commented] (LOG4J2-3032) Memory appender that can be flushed to another appender later

[ https://issues.apache.org/jira/browse/LOG4J2-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293240#comment-17293240 ] Caleb Cushing commented on LOG4J2-3032: --- Yeah, looks like a duplicate. > Memory a

[jira] [Commented] (LOG4J2-3034) Change Log format based on currently active level

[ https://issues.apache.org/jira/browse/LOG4J2-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293237#comment-17293237 ] Caleb Cushing commented on LOG4J2-3034: --- Wouldn't that change it for just 2 levels

[jira] [Commented] (LOG4J2-3034) Change Log format based on currently active level

[ https://issues.apache.org/jira/browse/LOG4J2-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293227#comment-17293227 ] Ralph Goers commented on LOG4J2-3034: - Yeah - you want the PatternSelector. {code:

[GitHub] [logging-log4j2] Marcono1234 commented on a change in pull request #471: LOG4J2-2948 Replace HashSet with IdentityHashMap in ParameterFormatter to detect cycles.

Marcono1234 commented on a change in pull request #471: URL: https://github.com/apache/logging-log4j2/pull/471#discussion_r585119540 ## File path: log4j-api/src/main/java/org/apache/logging/log4j/message/ParameterFormatter.java ## @@ -448,7 +450,7 @@ static String deepToString

[jira] [Commented] (LOG4J2-3032) Memory appender that can be flushed to another appender later

[ https://issues.apache.org/jira/browse/LOG4J2-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293219#comment-17293219 ] Ralph Goers commented on LOG4J2-3032: - This sounds suspiciously like a simpler varia

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #471: LOG4J2-2948 Replace HashSet with IdentityHashMap in ParameterFormatter to detect cycles.

carterkozak commented on a change in pull request #471: URL: https://github.com/apache/logging-log4j2/pull/471#discussion_r585008161 ## File path: log4j-api/src/main/java/org/apache/logging/log4j/message/ParameterFormatter.java ## @@ -538,24 +536,28 @@ private static void appe

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #471: LOG4J2-2948 Replace HashSet with IdentityHashMap in ParameterFormatter to detect cycles.

carterkozak commented on a change in pull request #471: URL: https://github.com/apache/logging-log4j2/pull/471#discussion_r585008161 ## File path: log4j-api/src/main/java/org/apache/logging/log4j/message/ParameterFormatter.java ## @@ -538,24 +536,28 @@ private static void appe

[GitHub] [logging-log4j2] vy commented on pull request #471: LOG4J2-2948 Replace HashSet with IdentityHashMap in ParameterFormatter to detect cycles.

vy commented on pull request #471: URL: https://github.com/apache/logging-log4j2/pull/471#issuecomment-788212187 @rgoers, would you mind reviewing the changes, please? Note that I don't create a new `HashSet` for each internal call, which has used to be the case. According to tests, this s

[GitHub] [logging-log4j2] vy opened a new pull request #471: LOG4J2-2948 Replace HashSet with IdentityHashMap in ParameterFormatter to detect cycles.

vy opened a new pull request #471: URL: https://github.com/apache/logging-log4j2/pull/471 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

[jira] [Commented] (LOG4J2-3028) OutputStreamManager does not clear buffer on exception

[ https://issues.apache.org/jira/browse/LOG4J2-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293119#comment-17293119 ] ASF subversion and git services commented on LOG4J2-3028: - Commi

[jira] [Commented] (LOG4J2-2948) Use IdentityHashMap for ParameterFormatter deja vu

[ https://issues.apache.org/jira/browse/LOG4J2-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293120#comment-17293120 ] ASF subversion and git services commented on LOG4J2-2948: - Commi

[jira] [Commented] (LOG4J2-2948) Use IdentityHashMap for ParameterFormatter deja vu

[ https://issues.apache.org/jira/browse/LOG4J2-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293114#comment-17293114 ] ASF subversion and git services commented on LOG4J2-2948: - Commi

[jira] [Updated] (LOG4J2-3034) Change Log format based on currently active level

[ https://issues.apache.org/jira/browse/LOG4J2-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-3034: -- Description: I'm not talking about `patternSelector`, I thought that was what I wanted, but I

[jira] [Created] (LOG4J2-3034) Change Log format based on currently active level

Caleb Cushing created LOG4J2-3034: - Summary: Change Log format based on currently active level Key: LOG4J2-3034 URL: https://issues.apache.org/jira/browse/LOG4J2-3034 Project: Log4j 2 Issue T

[jira] [Created] (LOG4J2-3033) LogBuilder don't require a message

Caleb Cushing created LOG4J2-3033: - Summary: LogBuilder don't require a message Key: LOG4J2-3033 URL: https://issues.apache.org/jira/browse/LOG4J2-3033 Project: Log4j 2 Issue Type: New Featur

[jira] [Created] (LOG4J2-3032) Memory appender that can be flushed to another appender later

Caleb Cushing created LOG4J2-3032: - Summary: Memory appender that can be flushed to another appender later Key: LOG4J2-3032 URL: https://issues.apache.org/jira/browse/LOG4J2-3032 Project: Log4j 2

[jira] [Updated] (LOG4J2-3031) Doc/Bug?/Feature: code configuration better

[ https://issues.apache.org/jira/browse/LOG4J2-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-3031: -- Description: I've had nothing but problems trying to get the code configuration working. I ha

[jira] [Created] (LOG4J2-3031) code configuration woes

Caleb Cushing created LOG4J2-3031: - Summary: code configuration woes Key: LOG4J2-3031 URL: https://issues.apache.org/jira/browse/LOG4J2-3031 Project: Log4j 2 Issue Type: Bug Repor

[CI][UNSTABLE] Logging/log4j/master#227 has test failures

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/master/227/ Project: master Date of build: Mon, 01 Mar 2021 15:22:04 + Build duration: 1 hr 27 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2 Failed:

[CI][UNSTABLE] Logging/log4j/release-2.x#249 has test failures

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/249/ Project: release-2.x Date of build: Mon, 01 Mar 2021 15:19:37 + Build duration: 1 hr 12 min and counting JUnit Tests Name: liquibase.ext.logging.log4

[jira] [Closed] (LOG4J2-3028) OutputStreamManager does not clear buffer on exception

[ https://issues.apache.org/jira/browse/LOG4J2-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3028. > OutputStreamManager does not clear buffer on exception > ---

[jira] [Resolved] (LOG4J2-3028) OutputStreamManager does not clear buffer on exception

[ https://issues.apache.org/jira/browse/LOG4J2-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3028. -- Resolution: Fixed I've committed this to both release-2.x for 2.14.1 and master for 3.x. Thank

[GitHub] [logging-log4j2] carterkozak closed pull request #470: [LOG4J2-3028] OutputStreamManager#flushBuffer always clears the buffer.

carterkozak closed pull request #470: URL: https://github.com/apache/logging-log4j2/pull/470 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[GitHub] [logging-log4j2] carterkozak commented on pull request #470: [LOG4J2-3028] OutputStreamManager#flushBuffer always clears the buffer.

carterkozak commented on pull request #470: URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-788031443 @vy Yep, I've taken care of merging this :-) This is an automated message from the Apache Git Service.

[jira] [Commented] (LOG4J2-3028) OutputStreamManager does not clear buffer on exception

[ https://issues.apache.org/jira/browse/LOG4J2-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292950#comment-17292950 ] ASF subversion and git services commented on LOG4J2-3028: - Commi

[jira] [Commented] (LOG4J2-3028) OutputStreamManager does not clear buffer on exception

[ https://issues.apache.org/jira/browse/LOG4J2-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292949#comment-17292949 ] ASF subversion and git services commented on LOG4J2-3028: - Commi

[GitHub] [logging-log4j2] carterkozak commented on pull request #470: [LOG4J2-3028] OutputStreamManager#flushBuffer always clears the buffer.

carterkozak commented on pull request #470: URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787966215 It looks like a build flake, I'll take care of the merge in the next hour This is an automated message

[GitHub] [logging-log4j2] jkozlowski commented on pull request #470: [LOG4J2-3028] OutputStreamManager#flushBuffer always clears the buffer.

jkozlowski commented on pull request #470: URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787941498 Hmm, there were merge conflicts, so I merged develop and now builds aren't green; I wonder if it's an actual issue or a flake? -

[GitHub] [logging-log4j2] jkozlowski commented on pull request #470: [LOG4J2-3028] OutputStreamManager#flushBuffer always clears the buffer.

jkozlowski commented on pull request #470: URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787872163 @vy should be done now This is an automated message from the Apache Git Service. To respond to the messa

[jira] [Assigned] (LOG4J2-2948) Use IdentityHashMap for ParameterFormatter deja vu

[ https://issues.apache.org/jira/browse/LOG4J2-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici reassigned LOG4J2-2948: - Assignee: Volkan Yazici > Use IdentityHashMap for ParameterFormatter deja vu >

[jira] [Commented] (LOG4J2-2948) Use IdentityHashMap for ParameterFormatter deja vu

[ https://issues.apache.org/jira/browse/LOG4J2-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292800#comment-17292800 ] Volkan Yazici commented on LOG4J2-2948: --- I will try sparing some time for this. I

[jira] [Closed] (LOG4J2-2963) make ObjectMessage and ParameterizedMessage extendable

[ https://issues.apache.org/jira/browse/LOG4J2-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici closed LOG4J2-2963. - Resolution: Abandoned Closing due to inactivity and insufficient rationale. > make ObjectMessag

[jira] [Commented] (LOG4J2-2952) How can I do the same thing using log4j2 like what I did when using logback with janino?

[ https://issues.apache.org/jira/browse/LOG4J2-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292796#comment-17292796 ] Volkan Yazici commented on LOG4J2-2952: --- [~rgoers], I don't see a reason to keep t

[GitHub] [logging-log4j2] vy commented on pull request #470: [LOG4J2-3028] OutputStreamManager#flushBuffer always clears the buffer.

vy commented on pull request #470: URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787803000 @jkozlowski, thanks so much for the contribution! Would you mind updating the `changes.xml` too, please? That is, ```xml OutputStreamManager does not clear buffer

[GitHub] [logging-log4j2] vy edited a comment on pull request #470: [LOG4J2-3028] OutputStreamManager#flushBuffer always clears the buffer.

vy edited a comment on pull request #470: URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787799822 @carterkozak, I am joining to the party late, sorry. What is the status of this PR? Can we merge it? (Note that the volunteer to merge might need to port this to `master`

[GitHub] [logging-log4j2] vy commented on pull request #470: [LOG4J2-3028] OutputStreamManager#flushBuffer always clears the buffer.

vy commented on pull request #470: URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787799822 @carterkozak, I am joining to the party late, sorry. What is the status of this PR? Can we merge it? This is an