lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <>
Subject Re: HTTP Status 503 - Server is shutting down
Date Sun, 14 Jul 2013 16:52:06 GMT
On 7/14/2013 6:43 AM, PeterKerk wrote:
> Hi Shawn,
> I'm also getting the HTTP Status 503 - Server is shutting down error when
> navigating to http://localhost:8080/solr-4.3.1/


> INFO: Deploying web application archive solr-4.3.1.war
> log4j:WARN No appenders could be found for logger
> (org.apache.solr.servlet.SolrD
> ispatchFilter).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See for
> more in
> fo.

THe file is used for JDK logging, which was the
default in Solr prior to version 4.3.0.  In older versions, jarfiles
were embedded in the .war file that set up slf4j to use
java.util.logging, also known as JDK logging because this logging
framework comes with Java.

Solr 4.3.0 and later does not have ANY slf4j jarfiles in the .war file,
so you need to put them in your classpath.  Jarfiles are included in the
example, in example/lib/ext, and those jarfiles set up logging to use
log4j, a much more flexible logging framework than JDK logging.

JDK logging is typically set up with a file called,
which I think you must use a system property to configure.  You aren't
using JDK logging, you are using log4j, which uses a file called

It appears that you have followed part of the instructions above and
copied jars from example/lib/ext to a lib directory on your classpath.
Now if you copy example/resources/ to the same place,
logging should work.  It will not log to the tomcat log, it will log to
the location specified in, which by default is
logs/solr.log relative to the current working directory.

As I already said on this thread, if you want Tomcat to be in control of
the logging, you must switch back to java.util.logging as described in
the wiki:


View raw message