[jira] [Commented] (LOG4J2-1080) Drop events when the RingBuffer is full

[ https://issues.apache.org/jira/browse/LOG4J2-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067581#comment-15067581 ] Sampath Kumar commented on LOG4J2-1080: --- I see this fix may introduce limitation in

[jira] [Commented] (LOG4J2-1080) Drop events when the RingBuffer is full

[ https://issues.apache.org/jira/browse/LOG4J2-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067280#comment-15067280 ] Remko Popma commented on LOG4J2-1080: - To answer my own question here: in my current

[jira] [Commented] (LOG4J2-1227) NullPointerException in MapLookup.lookup is the event is null

[ https://issues.apache.org/jira/browse/LOG4J2-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067204#comment-15067204 ] Remko Popma commented on LOG4J2-1227: - Looking at the diff for commit a2fb4c2be716568

[jira] [Commented] (LOG4J2-1229) Error creating logger

[ https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067169#comment-15067169 ] Gary Gregory commented on LOG4J2-1229: -- If you enable the status logger, you should

[jira] [Comment Edited] (LOG4J2-1229) Error creating logger

[ https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067163#comment-15067163 ] Dmitriy Dumanskiy edited comment on LOG4J2-1229 at 12/21/15 10:21 PM: -

[jira] [Commented] (LOG4J2-1229) Error creating logger

[ https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067163#comment-15067163 ] Dmitriy Dumanskiy commented on LOG4J2-1229: --- {code}

[jira] [Commented] (LOG4J2-1229) Error creating logger

[ https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067157#comment-15067157 ] Remko Popma commented on LOG4J2-1229: - Can you also attach your full log4j2.xml confi

[jira] [Commented] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

[ https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067155#comment-15067155 ] Remko Popma commented on LOG4J2-1221: - I just fixed LOG4J2-1212. > Dead lock observe

[jira] [Updated] (LOG4J2-1229) Error creating logger

[ https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Dumanskiy updated LOG4J2-1229: -- Description: I have a lot of VMs where everything is fine. But on some of them I get b

[jira] [Updated] (LOG4J2-1229) Error creating logger

[ https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Dumanskiy updated LOG4J2-1229: -- Description: I have a feeling it somehow related with access rights. Here is stacktrace

[jira] [Created] (LOG4J2-1229) Error creating logger

Dmitriy Dumanskiy created LOG4J2-1229: - Summary: Error creating logger Key: LOG4J2-1229 URL: https://issues.apache.org/jira/browse/LOG4J2-1229 Project: Log4j 2 Issue Type: Bug C

[jira] [Created] (LOG4J2-1228) Multiple footers written to file on system restart

Steve Davids created LOG4J2-1228: Summary: Multiple footers written to file on system restart Key: LOG4J2-1228 URL: https://issues.apache.org/jira/browse/LOG4J2-1228 Project: Log4j 2 Issue Ty

Jenkins build is back to stable : Log4j 2.x #1600

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

[ https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066670#comment-15066670 ] Sampath Kumar commented on LOG4J2-1221: --- Do you have Jira issue to track this Docum

[jira] [Resolved] (LOG4J2-1212) Update documentation of defaults for AsyncLogger.WaitStrategy AsyncLoggerConfig.WaitStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1212. - Resolution: Fixed Fix Version/s: 2.5.1 Thanks for the heads-up. Fixed in master in commit

Jenkins build is still unstable: Log4j 2.x #1599

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1227) NullPointerException in MapLookup.lookup is the event is null

[ https://issues.apache.org/jira/browse/LOG4J2-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066613#comment-15066613 ] ASF GitHub Bot commented on LOG4J2-1227: GitHub user olivierlemasle opened a pull

[jira] [Updated] (LOG4J2-1212) Update documentation of defaults for AsyncLogger.WaitStrategy AsyncLoggerConfig.WaitStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1212: Affects Version/s: 2.0-rc2 2.0 2.0.1

[jira] [Assigned] (LOG4J2-1212) Update documentation of defaults for AsyncLogger.WaitStrategy AsyncLoggerConfig.WaitStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1212: --- Assignee: Remko Popma > Update documentation of defaults for AsyncLogger.WaitStrategy > Asy

[jira] [Commented] (LOG4J2-1227) NullPointerException in MapLookup.lookup is the event is null

[ https://issues.apache.org/jira/browse/LOG4J2-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066595#comment-15066595 ] Olivier Lemasle commented on LOG4J2-1227: - This is due to commit a2fb4c2be716568.

[jira] [Created] (LOG4J2-1227) NullPointerException in MapLookup.lookup is the event is null

Olivier Lemasle created LOG4J2-1227: --- Summary: NullPointerException in MapLookup.lookup is the event is null Key: LOG4J2-1227 URL: https://issues.apache.org/jira/browse/LOG4J2-1227 Project: Log4j 2

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066585#comment-15066585 ] Joern Huxhorn commented on LOG4J2-1226: --- I'd argue that they still can. Just not if

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066533#comment-15066533 ] Remko Popma commented on LOG4J2-1226: - Ah. I spoke too soon. ObjectArrayMessage and O

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066525#comment-15066525 ] Remko Popma commented on LOG4J2-1226: - I don't understand how a ClassNotFoundExceptio

Jenkins build became unstable: Log4j 2.x #1598

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066516#comment-15066516 ] Joern Huxhorn commented on LOG4J2-1226: --- I do have a stacktrace but it's in Lilith

[jira] [Commented] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

[ https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066506#comment-15066506 ] Sampath Kumar commented on LOG4J2-1221: --- Sure Tomorrow i will be in office. Will at

[jira] [Comment Edited] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

[ https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066496#comment-15066496 ] Remko Popma edited comment on LOG4J2-1221 at 12/21/15 2:33 PM:

[jira] [Commented] (LOG4J2-1221) Dead lock observed in BlockingWaitStrategy in Log 4J

[ https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066496#comment-15066496 ] Remko Popma commented on LOG4J2-1221: - Docs are out of sync. Thanks for the reminder.

[jira] [Commented] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066466#comment-15066466 ] Joern Huxhorn commented on LOG4J2-1225: --- Ah, OK. Makes sense. Just thought it might

[jira] [Resolved] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1225. - Resolution: Won't Fix Assignee: Remko Popma I remember now why I did it this way: the Logge

[jira] [Closed] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1225. --- > MessageSupplier should extend Supplier > - > >

[jira] [Comment Edited] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066418#comment-15066418 ] Joern Huxhorn edited comment on LOG4J2-1225 at 12/21/15 12:53 PM: -

[jira] [Commented] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066418#comment-15066418 ] Joern Huxhorn commented on LOG4J2-1225: --- No specific reason at all. I was just surf

[jira] [Commented] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066358#comment-15066358 ] Remko Popma commented on LOG4J2-1225: - I don't oppose this but would like to understa

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066353#comment-15066353 ] Remko Popma commented on LOG4J2-1226: - First, do you have a stacktrace? Going over a

[jira] [Updated] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn updated LOG4J2-1226: -- Description: Right now, any Message instance used to call any log method are simply sent as th

[jira] [Created] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

Joern Huxhorn created LOG4J2-1226: - Summary: Message instances are simply serialized. They mustn't. Key: LOG4J2-1226 URL: https://issues.apache.org/jira/browse/LOG4J2-1226 Project: Log4j 2 Is

[jira] [Commented] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066300#comment-15066300 ] Joern Huxhorn commented on LOG4J2-1225: --- org.apache.logging.log4j.util.MessageSuppl

[jira] [Created] (LOG4J2-1225) MessageSupplier should extend Supplier

Joern Huxhorn created LOG4J2-1225: - Summary: MessageSupplier should extend Supplier Key: LOG4J2-1225 URL: https://issues.apache.org/jira/browse/LOG4J2-1225 Project: Log4j 2 Issue Type: Improv

[jira] [Comment Edited] (LOG4J2-1080) Drop events when the RingBuffer is full

[ https://issues.apache.org/jira/browse/LOG4J2-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066080#comment-15066080 ] Remko Popma edited comment on LOG4J2-1080 at 12/21/15 8:12 AM: