[jira] [Resolved] (AMQ-8142) Found SLF4J multiple bindings after adding activemq-all-5.6.0.jar file to jmeter/lib directory.

["Gary Tully (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-8142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-8142.
-----------------------------
    Resolution: Information Provided

these types of questions are better dealt with on the user list.

activemq-all is an 'uber' jar, it contains the classes from multiple other jars... as a convenience.

in place of activemq-all, pull in the individual jars that you need and leave the slf4j jar out.
ie: activemq-client.jar
jms spec jar etc.

> Found SLF4J multiple bindings after adding activemq-all-5.6.0.jar file to jmeter/lib directory.
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMQ-8142
>                 URL: https://issues.apache.org/jira/browse/AMQ-8142
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Yuliia Polishchuk
>            Priority: Major
>         Attachments: to ticket.png
>
>
> I need to run test for ActiveMQ on TC. 
>  For that I added activemq-all-5.6.0.jar to apache-jmeter-5.4/lib directory. But it causes warning on build logs for already existing jobs and broke it:
> {quote}SLF4J: Found binding in [jar:[file:/sti/apache-jmeter-5.4/lib/activemq-all-5.16.1.jar!/org/slf4j/impl/StaticLoggerBinder.class|file://sti/apache-jmeter-5.4/lib/activemq-all-5.16.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> {quote}
> Also in this case log4j2.xml file doesn't work with needed configuration.
>   
>  I found the solving for this issue: When multiple bindings are available on the class path, select one and only one binding you wish to use, and remove the other bindings. [http://www.slf4j.org/codes.html#multiple_bindings] 
> But I can't delete none of jar files, cause I need both of it for testing process. 
> How it can be solved in a different way? 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)