[jboss-jira] [JBoss JIRA] (JBAS-6532) TCLFilter doesn't work in jboss 5 with war's in any documented way

[Stéphane Raban (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651775#comment-12651775 ] 

Stéphane Raban commented on JBAS-6532:
--------------------------------------

The TCLMCFilter doesn't even work with WAR files in JBoss 5.1.0.GA

When several applications are deployed on the default instance server on jboss 5.1.0.GA it is not possible to separate logs in different files with log4j
All applications will log in all different files.

The filter TCLMCFIlter doesn't work, it lets everything through (like the old TCLFilter).
The class TCLMCFIlter.java has to be modify, there is a problem with the classloader, the methode getURLs doesn't work with 5.1.0, only for 5.0.0 version.
Then, filetring logj4 logging on war name is not possible :

Example :

<filter class="org.jboss.logging.filter.TCLFilter">
<param name="AcceptOnMatch" value="true"/>
<param name="DeployURL" value="wtf-exp.war"/>
</filter>
Could we do a new patch for the branch 5.1.0.GA ?

Relatives issues :
---------------------------
https://issues.jboss.org/browse/JBAS-6532
https://issues.jboss.org/browse/ORG-1259

Forum:
http://community.jboss.org/wiki/SeparatingApplicationLogs#comment-8603
                
> TCLFilter doesn't work in jboss 5 with war's in any documented way
> ------------------------------------------------------------------
>
>                 Key: JBAS-6532
>                 URL: https://issues.jboss.org/browse/JBAS-6532
>             Project: Legacy JBoss Application Server 6 
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-5.0.0.GA
>         Environment: jdk 6, linux
>            Reporter: robert lazarski
>            Assignee: jaikiran pai
>             Fix For: 6.0.0.M1
>
>         Attachments: JBAS-6532-test.patch, JBAS-6532.patch, jboss-logging-log4j.jar
>
>
> Reading this doc: 
> http://www.jboss.org/community/docs/DOC-12203
> Indicates a *-exp.war syntax is needed for TCLFilter war use, but there are no files of that type on my system running jboss 5. I've tried all the possible combinations I can think of, posted the problem to the forum, and the result is always that the file sizes and contents of the log files generated are exactly the same for the different war's, ie, no separated content. Here's my current config: 
> <appender name="penguinLog" class="org.apache.log4j.FileAppender">
>       <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"></errorHandler>
>       <param name="Append" value="false"/>
>       <param name="File" value="${jboss.server.home.dir}/log/penguinLog.log"/>
>       <layout class="org.apache.log4j.PatternLayout">
>          <param name="ConversionPattern" value="%d %-5p %c{1} %m%n"/>
>       </layout>
>       <filter class="org.jboss.logging.filter.TCLFilter">
>          <param name="AcceptOnMatch" value="true"/>
>          <param name="DeployURL" value="penguin"/>
>       </filter>
>    </appender>
>    <appender name="wtfLog" class="org.apache.log4j.FileAppender">
>       <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"></errorHandler>
>       <param name="Append" value="false"/>
>       <param name="File" value="${jboss.server.home.dir}/log/wtfLog.log"/>
>       <layout class="org.apache.log4j.PatternLayout">
>          <param name="ConversionPattern" value="%d %-5p %c{1} %m%n"/>
>       </layout>
>       <filter class="org.jboss.logging.filter.TCLFilter">
>          <param name="AcceptOnMatch" value="true"/>
>          <param name="DeployURL" value="wtf-exp.war"/>
>       </filter>
>    </appender>
>    <root>
>       <appender-ref ref="CONSOLE"/>
>       <appender-ref ref="FILE"/>
>       <appender-ref ref="penguinLog"/>
>       <appender-ref ref="wtfLog"/>
>    </root>
> 	

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira