-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
In the JBossLoggerFinder there is a check for the logger type:
final java.util.logging.Logger logger = java.util.logging.Logger.getLogger(name); if (!(logger instanceof org.jboss.logmanager.Logger)) { if (LOGGED.compareAndSet(false, true)) { logger.log(Level.ERROR, "The LogManager accessed before the \"java.util.logging.manager\" system property was set to \"org.jboss.logmanager.LogManager\". Results may be unexpected."); } }
If the log manager is loaded on two class loaders this might throw a false positive. We should compare the class names instead of the instance itself.
- is incorporated by
-
WFCORE-6078 Upgrade jboss-logmanager to 2.1.19.Final
- Closed
- relates to
-
WFLY-15863 ERROR: The LogManager accessed before the "java.util.logging.manager" system property was set to "org.jboss.logmanager.LogManager". Results may be unexpected.
- Closed
-
ELY-2182 LogManager warning when using the credential-store command
- Resolved