[
https://issues.apache.org/jira/browse/LOG4J2-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nik Everett closed LOG4J2-1817.
-------------------------------
Resolution: Not A Problem
Yes, that'll work. I should have seen that earlier. Thanks for pointing me in
the right direction.
> Can AbstractManager close managers after it has let go of the lock?
> -------------------------------------------------------------------
>
> Key: LOG4J2-1817
> URL: https://issues.apache.org/jira/browse/LOG4J2-1817
> Project: Log4j 2
> Issue Type: Wish
> Reporter: Nik Everett
> Priority: Minor
>
> I'm working on a Log4j2 appender that wants to make network calls to "flush"
> its appender during `releaseSub`. Right now these calls are done under the
> `AbstractManager.LOCK` which is causing me trouble. Because my system has
> other ordering requirements I'm seeing deadlocks, but even without these
> requirements it seems like bad form to hold this lock for as long as my
> `releaseSub` takes.
> I can certainly work around the issue, but, would it be possible to more
> releasing managers until after the lock is released?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
