[jboss-jira] [JBoss JIRA] Updated: (JBAS-3197) InvlidationManager$InvlidationGroupImpl produces incorrect log4j DEBGU level setting

[Dimitris Andreadis (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3197?page=all ]

Dimitris Andreadis updated JBAS-3197:
-------------------------------------

    Fix Version/s: JBossAS-4.0.6.CR1
                       (was: JBossAS-4.0.5.CR1)

> InvlidationManager$InvlidationGroupImpl produces incorrect log4j DEBGU level setting
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-3197
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3197
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JBoss Cache
>            Reporter: Ben Wang
>         Assigned To: Ben Wang
>            Priority: Minor
>             Fix For: JBossAS-4.0.6.CR1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> This is reported from a cusomter. The org.jboss.cache.InvalidationManager$InvalidationGroupImpl has log level tracing. However, log4j has problem to handle the InvalidationGroupImpl.getClass() since it has "$" sign to it. As a result, all the log are output as DEBUG even when the category is set as "INFO".
> Fix is not to use that. Instead, code it manually. 

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