[jboss-jira] [JBoss JIRA] Updated: (JBLOGGING-37) LogManager's level snapshot depends on indeterminate initialization order
[
https://jira.jboss.org/jira/browse/JBLOGGING-37?page=com.atlassian.jira.p...
]
David Lloyd updated JBLOGGING-37:
---------------------------------
Workaround Description: Initialize org.jboss.logmanager.Level manually before the
LogManager is initialized.
Workaround: [Workaround Exists]
LogManager's level snapshot depends on indeterminate
initialization order
-------------------------------------------------------------------------
Key: JBLOGGING-37
URL: https://jira.jboss.org/jira/browse/JBLOGGING-37
Project: JBoss Logging
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jboss-logging-logmanager
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 1.2.0.CR1-jboss-logmanager, 1.1.2.CR1-jboss-logmanager
This can cause level name lookups to fail if the logmanager was started up before the
jboss Level class was initialized. Instead of copying the levels from the parent
LogManager class, we should fix the list of available levels right off.
--
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