[jboss-jira] [JBoss JIRA] Commented: (JBLOGGING-44) Logging with a ResourceBundle finds message from another WAR
[
https://jira.jboss.org/jira/browse/JBLOGGING-44?page=com.atlassian.jira.p...
]
David Lloyd commented on JBLOGGING-44:
--------------------------------------
The way the work around the issue is by keeping a separate set of loggers per classloader.
When a logger is created, it's added to the set for the currently active TCCL. I
don't think this solution will work for us, per se, because they rely on parts of the
JDK logmanager which have inherent defects which we've disabled for this reason.
However I might be able to come up with another solution based on this idea...
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