[
https://issues.apache.org/jira/browse/AMQ-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776050#comment-13776050
]
Claus Ibsen commented on AMQ-4735:
----------------------------------
Are you running AMQ in a web app or something? Smells like the jetty container
has slf4j on its classpath and it conflicts with slf4j version of AMQ.
AMQ has recently upgraded to slf4j 1.7.x
> LinkageError in latest 5.9 snapshot
> -----------------------------------
>
> Key: AMQ-4735
> URL: https://issues.apache.org/jira/browse/AMQ-4735
> Project: ActiveMQ
> Issue Type: Bug
> Environment: activemq-5.9-20130919.101342-100
> Reporter: Lionel Cons
> Attachments: activemq.log
>
>
> When upgrading a test broker to the latest 5.9 snapshot I get:
> java.lang.LinkageError: loader constraint violation: when resolving method
> "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;"
> the class loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) of
> the current class, org/slf4j/LoggerFactory, and the class loader (instance of
> java/net/URLClassLoader) for resolved class,
> org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type
> org/slf4j/ILoggerFactory used in the signature
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
