You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Shlomi Hazan (JIRA)" <ji...@apache.org> on 2014/08/03 09:29:12 UTC
[jira] [Closed] (LOG4J2-757) apparent deadlock using basic config
with tomcat
[ https://issues.apache.org/jira/browse/LOG4J2-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shlomi Hazan closed LOG4J2-757.
-------------------------------
Resolution: Not a Problem
> apparent deadlock using basic config with tomcat
> ------------------------------------------------
>
> Key: LOG4J2-757
> URL: https://issues.apache.org/jira/browse/LOG4J2-757
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0
> Environment: windows
> Reporter: Shlomi Hazan
> Labels: deadlock
>
> Hi guys. I don't know what is the info relevant to this kind of issues and I dont want to blast with irrelevant stuff.
> What is probably interesting is that: I have a specific line of code that logs, that very consistently Deadlocks and when I remove the server runs smooth.
> tried various changes including taking out console appender, taking out asynch for sync appender, leaving only one appender... no go.
> Please list the information you find relevant and how to get it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org