[
https://issues.apache.org/jira/browse/LOG4J2-2837?focusedWorklogId=459511&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-459511
]
ASF GitHub Bot logged work on LOG4J2-2837:
------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Jul/20 20:11
Start Date: 15/Jul/20 20:11
Worklog Time Spent: 10m
Work Description: carterkozak opened a new pull request #388:
URL: https://github.com/apache/logging-log4j2/pull/388
Previously logging initialization would result in an AsyncLoggerContext
initializing an AsyncLoggerDisruptor, which would access a logger from
JUL, starting the process again. This change avoids recursive calls with
a state check.
----------------------------------------------------------------
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 go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 459511)
Remaining Estimate: 0h
Time Spent: 10m
> Fully asynchronous logging results in two disruptors being created
> ------------------------------------------------------------------
>
> Key: LOG4J2-2837
> URL: https://issues.apache.org/jira/browse/LOG4J2-2837
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.13.2
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> While looking into a hang (unsure if it's related) I found that there were
> two "Log4j2-TF-AsyncLogger[context]-*" threads running.
> We end up re-initializing the logger internally when a Disruptor instance is
> created because it also requests a logger. It doesn't appear as though this
> results in an incorrect background thread ID, but the intermediate thread is
> leaked.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
