[jboss-jira] [JBoss JIRA] (LOGMGR-89) LogContext's root logger is not created with a strong child hash map when strong=true

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on LOGMGR-89:
-----------------------------------------------

mark yarborough <myarboro at redhat.com> changed the Status of [bug 1052198|https://bugzilla.redhat.com/show_bug.cgi?id=1052198] from VERIFIED to CLOSED

> LogContext's root logger is not created with a strong child hash map when strong=true
> -------------------------------------------------------------------------------------
>
>                 Key: LOGMGR-89
>                 URL: https://issues.jboss.org/browse/LOGMGR-89
>             Project: JBoss Log Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: This issue happens on 32-bit JVMs, and I can reproduce it on JDK 6 (64-bit)
>            Reporter: Kyle Lape
>            Assignee: David Lloyd
>             Fix For: 1.2.3.GA, 1.3.3.Final, 1.4.4.Final, 1.5.2.Final, 2.0.0.Beta1
>
>
> When deploying an application in EAP 6 that has a log4j.xml that is deployed by the logging subsystem, it seems that the LogContext is somehow losing a reference to a custom logger, causing all configuration for that logger to be lost.
> Given this configuration
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
> <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="true">
>   <appender name="SAMPLE_APP" class="org.apache.log4j.RollingFileAppender">
>     <param name="File" value="${jboss.server.log.dir}/SampleApp.log"/>
>     <param name="MaxFileSize" value="2MB"/>
>     <param name="MaxBackupIndex" value="5"/>
>     <param name="Append" value="true"/>
>     <layout class="org.apache.log4j.PatternLayout">
>       <param name="ConversionPattern" value="%d %c [%t] %-5p - %m%n"/>
>     </layout>
>   </appender>
>   <appender name="SAMPLE_APP_MDB" class="org.apache.log4j.RollingFileAppender">
>     <param name="File" value="${jboss.server.log.dir}/SampleApp-MDB.log"/>
>     <param name="MaxFileSize" value="2MB"/>
>     <param name="MaxBackupIndex" value="5"/>
>     <param name="Append" value="true"/>
>     <layout class="org.apache.log4j.PatternLayout">
>       <param name="ConversionPattern" value="%d %c [%t] %-5p - %m%n"/>
>     </layout>
>   </appender>
>   <logger name="com.redhat" additivity="false">
>     <level value="TRACE"/>
>     <appender-ref ref="SAMPLE_APP_MDB"/>
>   </logger>
>   <root>
>     <priority value="TRACE"/>
>     <appender-ref ref="SAMPLE_APP"/>
>   </root>
> </log4j:configuration>
> {code}
> Every log message ends up in {{SAMPLE_APP}}, regardless of which logger was used.  One message like this is also printed to the log:
> {noformat}
> 11:33:00,110 INFO  [stdout] (Finalizer) log4j: Finalizing appender named [SAMPLE_APP_MDB].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)