[
https://issues.apache.org/jira/browse/UIMA-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280056#comment-14280056
]
Aleksandar Dimitrov commented on UIMA-3633:
-------------------------------------------
This bug is *NOT* fixed as of UIMA-AS 2.6.0. Using SLF4J (and depending on it
in your {{pom.xml}}, as well as on {{uimaj-as-activemq}}) you will still get
the following warning message:
{quote}
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
\[jar:file:/home/aleks/.m2/repository/ch/qos/logback/logback-classic/1.1.2/logback-classic-1.1.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
\[jar:file:/home/aleks/.m2/repository/org/apache/activemq/activemq-all/5.7.0/activemq-all-5.7.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type
\[ch.qos.logback.classic.util.ContextSelectorStaticBinder]
{quote}
Additionally, parts of my {{logback.xml}} configuration are ignored, and the
Spring Framework's log4j doesn't get configured correctly, resulting in the
following warning message (and missing logs:\)
{quote}
log4j:WARN No appenders could be found for logger
(org.springframework.context.support.FileSystemXmlApplicationContext).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
{quote}
See also [my Email to
UIMA-user|http://mail-archives.apache.org/mod_mbox/uima-user/201412.mbox/browser].
The current workaround for me is to use the following to include UIMA-AS in my
{{pom.xml}}:
{code:xml}
<dependency>
<groupId>org.apache.uima</groupId>
<artifactId>uimaj-as-activemq</artifactId>
<version>2.6.0</version>
<exclusions>
<exclusion>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.7.0</version>
</dependency>
{code}
This is a direct result of the ActiveMQ bug
[AMQ-5009|https://issues.apache.org/jira/browse/AMQ-5009], which has since lead
to a documentation update on the [AMQ download
page|http://activemq.apache.org/activemq-5100-release.html], advising users to
not use {{activemq-all}} in their Maven dependencies if better control over the
dependencies is a requirement.
I would suggest to switch away from directly depending on {{activemq-all}} in
{{uimaj-as-activemq}}, and include {{activemq-core}}, or {{activemq-client}}
and {{activemq-broker}} as required. I think that given the current situation
this is the best way to avoid shadowing ActiveMQ's dependencies due to its use
of the Maven-Shade plugin.
> Fix SLF4J warnings in UIMA-AS
> -----------------------------
>
> Key: UIMA-3633
> URL: https://issues.apache.org/jira/browse/UIMA-3633
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.4.2AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Minor
> Fix For: 2.6.0AS
>
>
> Fix multiple SLF4J binding errors due to the inclusion of
> activemq-all.jar and slf4j-log4j12-1.6.4.jar
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
