[jira] [Work logged] (LOG4J2-2899) LogEventWrapper.getThread only works on the first invocation

2020-07-18 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2899?focusedWorklogId=460775&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-460775 ] ASF GitHub Bot logged work on LOG4J2-2899: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers edited a comment on pull request #390: LOG4J2-2899: Fix log4j-1.2-api LogEventWrapper thread data accessors

2020-07-18 Thread GitBox
rgoers edited a comment on pull request #390: URL: https://github.com/apache/logging-log4j2/pull/390#issuecomment-660576958 Yeah, I don't think it can be guaranteed that the methods will always be called on the same thread. But I am also noticing that the method stores the thread it found

[jira] [Work logged] (LOG4J2-2899) LogEventWrapper.getThread only works on the first invocation

2020-07-18 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2899?focusedWorklogId=460774&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-460774 ] ASF GitHub Bot logged work on LOG4J2-2899: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers commented on pull request #390: LOG4J2-2899: Fix log4j-1.2-api LogEventWrapper thread data accessors

2020-07-18 Thread GitBox
rgoers commented on pull request #390: URL: https://github.com/apache/logging-log4j2/pull/390#issuecomment-660576958 Yeah, I don't think it can be guaranteed that the methods will always be called on the same thread. This is

[jira] [Commented] (LOG4J2-2899) LogEventWrapper.getThread only works on the first invocation

2020-07-18 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160513#comment-17160513 ] Carter Kozak commented on LOG4J2-2899: -- https://github.com/apache/logging-log4j2/pu

[jira] [Work logged] (LOG4J2-2899) LogEventWrapper.getThread only works on the first invocation

2020-07-18 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2899?focusedWorklogId=460744&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-460744 ] ASF GitHub Bot logged work on LOG4J2-2899: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] carterkozak commented on pull request #390: LOG4J2-2899: Fix log4j-1.2-api LogEventWrapper thread data accessors

2020-07-18 Thread GitBox
carterkozak commented on pull request #390: URL: https://github.com/apache/logging-log4j2/pull/390#issuecomment-660516966 @rgoers, I'd appreciate your feedback on this change when you have time. I'm primarily interested in whether or not you think it's reasonable to replace `Thread.getAllS

[jira] [Assigned] (LOG4J2-2899) LogEventWrapper.getThread only works on the first invocation

2020-07-18 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2899: Assignee: Carter Kozak > LogEventWrapper.getThread only works on the first invocation > -

[jira] [Work logged] (LOG4J2-2899) LogEventWrapper.getThread only works on the first invocation

2020-07-18 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2899?focusedWorklogId=460742&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-460742 ] ASF GitHub Bot logged work on LOG4J2-2899: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] carterkozak opened a new pull request #390: LOG4J2-2899: Fix log4j-1.2-api LogEventWrapper thread data accessors

2020-07-18 Thread GitBox
carterkozak opened a new pull request #390: URL: https://github.com/apache/logging-log4j2/pull/390 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[jira] [Created] (LOG4J2-2899) LogEventWrapper.getThread only works on the first invocation

2020-07-18 Thread Carter Kozak (Jira)
Carter Kozak created LOG4J2-2899: Summary: LogEventWrapper.getThread only works on the first invocation Key: LOG4J2-2899 URL: https://issues.apache.org/jira/browse/LOG4J2-2899 Project: Log4j 2

[jira] [Commented] (LOG4J2-2898) Avoid initializing volatile fields to their default values

2020-07-18 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160462#comment-17160462 ] ASF subversion and git services commented on LOG4J2-2898: - Commi

[jira] [Commented] (LOG4J2-2898) Avoid initializing volatile fields to their default values

2020-07-18 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160464#comment-17160464 ] ASF subversion and git services commented on LOG4J2-2898: - Commi

[jira] [Commented] (LOG4J2-2898) Avoid initializing volatile fields to their default values

2020-07-18 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160463#comment-17160463 ] ASF subversion and git services commented on LOG4J2-2898: - Commi

[jira] [Resolved] (LOG4J2-2898) Avoid initializing volatile fields to their default values

2020-07-18 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2898. -- Resolution: Fixed > Avoid initializing volatile fields to their default values > -

[jira] [Closed] (LOG4J2-2898) Avoid initializing volatile fields to their default values

2020-07-18 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2898. > Avoid initializing volatile fields to their default values > ---

[jira] [Commented] (LOG4J2-2898) Avoid initializing volatile fields to their default values

2020-07-18 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160458#comment-17160458 ] ASF subversion and git services commented on LOG4J2-2898: - Commi

[GitHub] [logging-log4j2] carterkozak merged pull request #367: avoid initialize 'volatile' fields with default values

2020-07-18 Thread GitBox
carterkozak merged pull request #367: URL: https://github.com/apache/logging-log4j2/pull/367 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

[jira] [Assigned] (LOG4J2-2898) Avoid initializing volatile fields to their default values

2020-07-18 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2898: Assignee: Carter Kozak > Avoid initializing volatile fields to their default values > ---

[jira] [Created] (LOG4J2-2898) Avoid initializing volatile fields to their default values

2020-07-18 Thread Carter Kozak (Jira)
Carter Kozak created LOG4J2-2898: Summary: Avoid initializing volatile fields to their default values Key: LOG4J2-2898 URL: https://issues.apache.org/jira/browse/LOG4J2-2898 Project: Log4j 2

[GitHub] [logging-log4j2] carterkozak commented on pull request #367: avoid initialize 'volatile' fields with default values

2020-07-18 Thread GitBox
carterkozak commented on pull request #367: URL: https://github.com/apache/logging-log4j2/pull/367#issuecomment-660502501 I've created a ticket for this contribution: https://issues.apache.org/jira/browse/LOG4J2-2898 Merging momentarily.