[jboss-jira] [JBoss JIRA] (JBLOGGING-70) JBoss LogManager detection is still incorrect
Aaron Douglas (Commented) (JIRA)
jira-events at lists.jboss.org
Thu Nov 17 09:15:42 EST 2011
[ https://issues.jboss.org/browse/JBLOGGING-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643698#comment-12643698 ]
Aaron Douglas commented on JBLOGGING-70:
----------------------------------------
I'm fairly certain that it is class path related as well since I am loading the newer JBoss Logging JAR in my WAR, attempting to override what's provided by JBoss EAP 5.0.
Are you recommending I update/replace the JBoss logging in the server lib folder? I had assumed JBLOGGING-47 indicated that JBLOGGING-70 was the fix for it but I suspect it was never tested according to the comments. Ultimately I need to upgrade JBoss but until there is an EAP 6, I am stuck with 5.0.
> 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