Note that there are some explanatory texts on larger screens.

plurals
  1. POError Starting Jetty-Service (Solr)
    text
    copied!<p><strong>Update:</strong> I installed the 32bit JDK and the service starts fine now. No idea why though. The machine it was failing on was 64bit...</p> <p><strong>Update2:</strong> So installing the 32bit JDK will allow the service to install, but solr will not run. There is a StackOverflowException and NullPointer Excpetions in the logs.</p> <p>I am trying to run Jetty as a service on Windows 7 64bit. I have it running on a very similar machine just fine, but on the second I am getting errors I have not been able to resolve.</p> <p>The service installs fine, however when you try to start it you get the message in the console: The Jetty6-Service service was launched, but failed to start.</p> <p><img src="https://i.stack.imgur.com/sGLip.png" alt="enter image description here"></p> <p>This is the related contents in the jetty-service.log:</p> <pre><code>STATUS | wrapper | 2011/02/16 12:50:07 | Starting the Jetty6-Service service... STATUS | wrapper | 2011/02/16 12:50:07 | --&gt; Wrapper Started as Service DEBUG | wrapper | 2011/02/16 12:50:07 | Using tick timer. DEBUG | wrapperp | 2011/02/16 12:50:07 | server listening on port 32000. STATUS | wrapper | 2011/02/16 12:50:07 | Launching a JVM... DEBUG | wrapper | 2011/02/16 12:50:07 | command: "java" -Djetty.home=../ -Djetty.logs=../logs -Dsolr.solr.home=C:/solr/ -Xms5m -Xmx64m -Djava.library.path="../lib/win32/" -classpath "../lib/win32/jetty-win32-service-java-6.1.26.jar;../lib/win32/wrapper.jar;../lib/jetty-6.1.3.jar;../lib/jetty-util-6.1.3.jar;../lib/servlet-api-2.5-6.1.3.jar;../start.jar" -Dwrapper.key="c5CIhIjsO0gmMcTE" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=4708 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.mortbay.jetty.win32service.JettyServiceWrapperListener ../etc/jetty.xml FATAL | wrapper | 2011/02/16 12:50:07 | Unable to execute Java command. The system cannot find the file specified. (0x2) FATAL | wrapper | 2011/02/16 12:50:07 | "java" -Djetty.home=../ -Djetty.logs=../logs -Dsolr.solr.home=C:/solr/ -Xms5m -Xmx64m -Djava.library.path="../lib/win32/" -classpath "../lib/win32/jetty-win32-service-java-6.1.26.jar;../lib/win32/wrapper.jar;../lib/jetty-6.1.3.jar;../lib/jetty-util-6.1.3.jar;../lib/servlet-api-2.5-6.1.3.jar;../start.jar" -Dwrapper.key="c5CIhIjsO0gmMcTE" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=4708 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.mortbay.jetty.win32service.JettyServiceWrapperListener ../etc/jetty.xml FATAL | wrapper | 2011/02/16 12:50:07 | Critical error: wait for JVM process failed ERROR | wrapper | 2011/02/16 12:50:09 | The Jetty6-Service service was launched, but failed to start. </code></pre> <p>The one difference that I know of between the two machines is that the one that is not working had Tomcat installed at one point which it no longer does.</p> <p>I have tried the following:</p> <ol> <li>Uninstalled all copies of the Java JDK and JRE</li> <li>Reinstalled the latest Java JDK - jdk1.6.0_24 which installs the associated JRE</li> <li>Tried setting JAVA_HOME to C:\Program Files\Java\jdk1.6.0_24</li> <li>Googled all error messages</li> <li>I can run java -version in the console without error</li> </ol> <p>In case someone is looking for more information on running Jetty as a service, check out:</p> <ol> <li><a href="http://docs.codehaus.org/display/JETTY/Win32Wrapper" rel="nofollow noreferrer">http://docs.codehaus.org/display/JETTY/Win32Wrapper</a></li> <li><a href="http://technologyenablingbusiness.blogspot.com/2010/12/solr-on-jetty-as-windows-service.html" rel="nofollow noreferrer">http://technologyenablingbusiness.blogspot.com/2010/12/solr-on-jetty-as-windows-service.html</a></li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload