logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-757) apparent deadlock using basic config with tomcat
Date Sun, 03 Aug 2014 06:44:11 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083890#comment-14083890

Remko Popma commented on LOG4J2-757:

It would be ideal if you could attach a small project that demonstrates the issue. 
If that's difficult, please give as much info as possible that might allow us to reproduce
the issue:
Log4j2 version, tomcat version, os name & version, java version, your log4j2.xml and web.xml?

> 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

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

View raw message