[jboss-jira] [JBoss JIRA] Commented: (JBLOGGING-44) Logging with a ResourceBundle finds message from another WAR

[David Lloyd (JIRA)]

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

David Lloyd commented on JBLOGGING-44:
--------------------------------------

Maybe a hybrid solution where each deployment gets its own log context, but the handlers are somehow cloned from the system log context?  Though in this case, the system log configuration wouldn't work because the loggers themselves are actually isolated.

I can't think of any other way to create isolated Logger instances offhand.  I don't see how it could work under any circumstances.

> Logging with a ResourceBundle finds message from another WAR
> ------------------------------------------------------------
>
>                 Key: JBLOGGING-44
>                 URL: https://jira.jboss.org/jira/browse/JBLOGGING-44
>             Project: JBoss Logging
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Stan Silvert
>            Assignee: David Lloyd
>         Attachments: bar.war, foo.war
>
>
> I'm attaching two WARs to demonstrate.  foo.war and bar.war are identical except for the message in the resource bundle.
> Hit
> http://localhost:8080/foo/index.jsp
> http://localhost:8080/bar/index.jsp
> http://localhost:8080/foo/index.jsp
> Both will output the correct message to the browser when the lookup is done from ResourceBundle.getString().  But the log message it sends will not always be correct.  "bar" always wins.  As soon as "bar" has been called then "foo" can no longer log the correct message.

-- 
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