[jboss-jira] [JBoss JIRA] (JBLOGGING-70) JBoss LogManager detection is still incorrect

[David Lloyd (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBLOGGING-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643718#comment-12643718 ] 

David Lloyd commented on JBLOGGING-70:
--------------------------------------

Not necessarily, but one of two things must be happening:

# The version of jboss-logging.jar being used is not the one you're bundling.
# You've got another jboss-logmanager.jar somewhere which is partially or fully overriding the one in the container.

I really don't think that #2 could be it because there's an explicit check to enforce the following:

# That the installed system logmanager class is exactly equal to the JBoss LogManager class visible from jboss-logging.jar
# That the installed JBoss LogManager includes the Logger.AttachmentKey class (which did not turn up until 1.1.0.x)
# That the installed JBoss LogManager's Logger.AttachmentKey class is exactly equal to the one visible from jboss-logging.jar

The exception you are seeing is triggered after these checks would take place, which is impossible as far as I can tell.  The only possible conclusion I can see is that the check *isn't* taking place because the version of jboss-logging.jar which includes it (only the latest SNAPSHOT) is not being executed; instead some other earlier one is.  I figure there must be a jboss-logging.jar somewhere in the deployers/ directory or something which is taking precedence for some reason.

                
> 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