[jboss-jira] [JBoss JIRA] (JBLOGGING-70) JBoss LogManager detection is still incorrect
Aaron Douglas (Commented) (JIRA)
jira-events at lists.jboss.org
Wed Nov 16 20:36:40 EST 2011
[ https://issues.jboss.org/browse/JBLOGGING-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643580#comment-12643580 ]
Aaron Douglas commented on JBLOGGING-70:
----------------------------------------
I verified that I do not have a second jboss-logmanager (or repackaged log manager) in my deployment. Everything in my container is standard JBoss EAP 5.0. I had to include the JBoss Logging 3.1.0.CR1 with my WAR because Infinispan 5.1 requires the newer logging package. My WAR's class loader is set to override the server lib with the WEB-INF/lib JARs. I can't provide a newer log manager in my WAR because it complains about JBoss already having one set up.
> 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
More information about the jboss-jira
mailing list