On 5/9/2013 12:54 PM, Jason Hellman wrote:
If you nab the jars in example/lib/ext and place them within the appropriate
folder in Tomcat (and this will somewhat depend on which version of Tomcat you
are using…let's presume tomcat/lib as a brute-force approach) you should be
back in business.
On May 9, 2013, at 11:41 AM, richardg <richa...@dvdempire.com> wrote:
Thanks for responding. My issue is I've never changed anything w/ logging, I
have always used the built in Juli. I've never messed w/ any jar files,
just had edit the logging.properties file. I don't know where I would get
the jars for juli or where to put them, if that is what is needed. I had
read what you posted before I just can't make any sense of it.
I've been looking into this a little bit. Tomcat's juli is an apache
reimplementation of java.util.logging. Solr uses SLF4J, but before 4.3,
Solr's slf4j was bound to java.util.logging ... which I would bet was
being intercepted by tomcat and sent through the juli config.
With 4.3, SLF4J is bound to log4j by default. If you stick with this
binding, then you need to configure log4j instead of juli.
Richard, you could go back to java.util.logging (the way earlier
versions had it) with this procedure, and this will probably restore the
ability to configure logging with juli.
- Delete the following jars from Solr's example lib/ext:
-- jul-to-slf4j-1.6.6.jar
-- log4j-1.2.16.jar
-- slf4j-log4j12-1.6.6.jar
- Download slf4j version 1.6.6 from their website.
- Copy the following jars from the download into lib/ext:
-- log4j-over-slf4j-1.6.6.jar
-- slf4j-jdk14-1.6.6.jar
- Copy all jars in lib/ext to tomcat's lib directory.
http://www.slf4j.org/dist/
http://www.slf4j.org
Alternatively, you could copy the jars from lib/ext to a directory in
your classpath, or add Solr's lib/ext to your classpath.
If you want to upgrade to the newest slf4j, you can, you'll just have to
use the new version for all slf4j jars.
Please let me know whether this worked for you so we can get a proper
procedure up on the wiki.
Thanks,
Shawn
