[jboss-jira] [JBoss JIRA] Commented: (JBLOGGING-39) TCLMCFilter does not work with AsyncAppender

Tue Apr 6 04:12:37 EDT 2010

    [ https://jira.jboss.org/jira/browse/JBLOGGING-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12523932#action_12523932 ] 

Alexis Hassler commented on JBLOGGING-39:
-----------------------------------------

What does "Rejected" means : not reproduced ? not a bug ? ... ?

At least, you should change the wiki in order to explain that TCLMCFilter is not compatible with the AsyncAppender. 
Note that this appender is by default on production configuration in JBoss EAP.

> TCLMCFilter does not work with AsyncAppender
> --------------------------------------------
>
>                 Key: JBLOGGING-39
>                 URL: https://jira.jboss.org/jira/browse/JBLOGGING-39
>             Project: JBoss Logging
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jboss-logging-log4j
>    Affects Versions: 2.1.1.GA-jboss-logging
>         Environment: Linux Ubuntu 9.10, JBoss 5.1.0, Logging 2.1.1, JDK 6
>            Reporter: Alexis Hassler
>            Assignee: David Lloyd
>
> I followed http://community.jboss.org/wiki/SeparatingApplicationLogs to use the new TCLMCFilter in JBoss 5.1.0. It works fine when I associate the appender directly to the root logger. When I associate the appender to a AsyncAppender, there is no more log.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira