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

[Brian Stansberry (JIRA)]

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

Brian Stansberry resolved JBAS-3924.
------------------------------------

    Fix Version/s: JBossAS-4.0.5.SP1 
                   JBossAS-3.2.8.SP2
       Resolution: Done

Resolved by converting any '$' to a '.'

> InvlidationManager$InvlidationGroupImpl produces incorrect log4j DEBGU level setting
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-3924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3924
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Ben Wang
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 , JBossAS-3.2.8.SP2
>
>   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