[jboss-jira] [JBoss JIRA] (JBLOGGING-70) JBoss LogManager detection is still incorrect
[
https://issues.jboss.org/browse/JBLOGGING-70?page=com.atlassian.jira.plug...
]
Aaron Douglas commented on JBLOGGING-70:
----------------------------------------
Compiled HEAD of the repo and built CRS SNAPSHOT - same deal unfortunately. Looks like I
had the same code as in CR1. Anything I should try next or do you need any more details?
JBoss LogManager detection is still incorrect
---------------------------------------------
Key: JBLOGGING-70
URL: https://issues.jboss.org/browse/JBLOGGING-70
Project: JBoss Logging
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.0.0.GA
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 3.0.1.GA, 3.1.0.Beta1
The detection in LoggerProviders is insufficient because the failure can simply be
deferred, resulting in exceptions like this:
{noformat}
java.lang.NoSuchMethodError:
org.jboss.logmanager.LogContext.getAttachment(Ljava/lang/String;Lorg/jboss/logmanager/Logger$AttachmentKey;)Ljava/lang/Object;
at
org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:52)
at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:47)
at org.jboss.logging.Logger.getLogger(Logger.java:2164)
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2263)
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2215)
at org.infinispan.util.logging.LogFactory.getLog(LogFactory.java:41)
[...]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira