On 2/16/2017 11:31 PM, Prashant Saraswat wrote: > *On Solr 6.3 onwards, the following logs are displayed:*
<snip> > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/home/ubuntu/apache-tomcat-8.5.11/lib/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/home/ubuntu/apache-tomcat-8.5.11/webapps/solr/WEB-INF/lib/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. The information about what is wrong here is right in the log. I have quoted the relevant portion above. This is slf4j complaining about finding its binary code twice. There are no differences between 6.3 and 6.2 in how logging jars are included. You'll need to delete one set of logging jars. This is not a Solr issue, or even a Tomcat issue. It appears that you have copied some of the jars to two places. The locations are in your log. I was not involved in the Solr project when the decision was made to include Jetty. It has been included with Solr for many years. It was already there when I first downloaded 1.4.0 back in early 2010, and I've been using it all this time without any issues related to the container. With 5.0, we chose to enforce the container choice more strictly. Now there are far fewer deployment options, so Solr is a lot easier for this mailing list to support. Thanks, Shawn
