-
Bug
-
Resolution: Done
-
Major
-
3.0.0.GA
-
None
-
None
The detection in LoggerProviders is insufficient because the failure can simply be deferred, resulting in exceptions like this:
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)
[...]
- relates to
-
JBLOGGING-47 Support EAP 5.1 in JBoss Logging 3
-
- Resolved
-
