jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Edelson <jus...@justinedelson.com>
Subject Re: newbie question: service_unvailable error
Date Sun, 21 Nov 2010 16:25:11 GMT
On Sun, Nov 21, 2010 at 11:06 AM, Mark Phillips
<mark.phillips@mophilly.com> wrote:
> On Nov 21, 2010, at 7:02 AM, Justin Edelson wrote:
>
>> Have you looked at the log file?
>
> Yes and no. Yes, in that I have looked at them and no insofar as to understanding what
I am seeing.
>
> One question does come to mind: what is "org.mortby.log"?
>
> Here is what I have:
>
> In terminal window:
>> java -jar jackrabbit-standalone-2.1.2.jar
> Welcome to Apache Jackrabbit!
> -------------------------------
> Using repository directory jackrabbit
> Writing log messages to jackrabbit/log
> Starting the server...
> Apache Jackrabbit is now running at http://localhost:8080/
>
> In Firefox, I get:
>        http error 503
>        problem accessing /. Reason:
>        service_unavailable
>
> There is nothing in the accessl.og or the jackrabbit.log files. However, there is the
following in the jetty.log file:
>
> 21.11.2010 07:48:12 *INFO * log: Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log)
via org.mortbay.log.Slf4jLog
> 21.11.2010 07:48:12 *INFO * log: jetty-6.1.x
> 21.11.2010 07:48:12 *WARN * log: Web application not found jackrabbit-standalone.jar
> 21.11.2010 07:48:12 *WARN * log: Failed startup of context org.mortbay.jetty.webapp.WebAppContext@2efb56b1{/,jackrabbit-standalone.jar}
> java.io.FileNotFoundException: jackrabbit-standalone.jar
>        at org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:965)
>        at org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:800)
>        at org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
>        at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:457)
>        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>        at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
>        at org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
>        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>        at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
>        at org.mortbay.jetty.Server.doStart(Server.java:224)
>        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>        at org.apache.jackrabbit.standalone.Main.run(Main.java:181)
>        at org.apache.jackrabbit.standalone.Main.main(Main.java:66)
> 21.11.2010 07:48:12 *INFO * log: Opened /Volumes/Iomega_HDD/Mophilly Projects/Instinct
Systems/JackRabbit/jackrabbit/log/access.log.2010-11-21
> 21.11.2010 07:48:12 *INFO * log: Started SocketConnector@0.0.0.0:8080
>
> Thanks for taking a look at this.
>
>  - Mark

This error message is telling you that Jackrabbit standalone's
embedded instance of Jetty is being configured with the wrong file
name (jackrabbit-standalone.jar vs. jackrabbit-standalone-2.1.2.jar. I
don't know why this is happening; it doesn't for me (on OS X 10.6.3).
If you debug the code in org.apache.jackrabbit.standalone.Main
(specifically the run method), you should be able to see why this is
happening and report it as a bug. Here's the relevant code:

String defaultFile = "jackrabbit-standalone.jar";

URL location = Main.class.getProtectionDomain().getCodeSource().getLocation();
if (location != null && "file".equals(location.getProtocol())) {
            File file = new File(location.getPath());
            if (file.isFile()) {
                defaultFile = location.getPath();
            }
}

org.mortbay is the package structure under which the Jetty web
container lives. org.mortbay.log is the package which contains Jetty's
logging utilities.

Justin

Mime
View raw message