In 5.0 "the new way" is to not use a servlet container, just use the start/stop scripts.
you should find a ...solr/bin/solr that you use to start/stop/whatever. You can still run with a "normal" servlet container, but is there a particular reason you need to? If not, just use the start/stop commends from the script. Best, Erick On Fri, Feb 27, 2015 at 9:59 AM, <h15...@mailas.com> wrote: > I'm trying a 1st deploy of Solr 5.0.0 in Jetty9 > (jetty-distribution-9.2.9.v20150224). > > I've installed Jetty9 > > /etc/init.d/jetty check > Checking arguments to Jetty: > START_INI = /usr/local/etc/jetty/base/start.ini > START_D = /usr/local/etc/jetty/base/start.d > JETTY_HOME = /usr/local/jetty > JETTY_BASE = /usr/local/etc/jetty/base > JETTY_CONF = /usr/local/jetty/etc/jetty.conf > JETTY_PID = /usr/local/etc/jetty/run/jetty.pid > JETTY_START = /usr/local/jetty/start.jar > JETTY_LOGS = /var/log/jetty > JETTY_STATE = /usr/local/etc/jetty/run/jetty.state > CLASSPATH = > JAVA = /usr/lib64/jvm/java-openjdk/bin/java > JAVA_OPTIONS = -Djetty.logs=/var/log/jetty > -Djetty.home=/usr/local/jetty -Djetty.base=/usr/local/etc/jetty/base > -Djava.io.tmpdir=/tmp > JETTY_ARGS = jetty.state=/usr/local/etc/jetty/run/jetty.state > jetty-logging.xml jetty-started.xml > RUN_CMD = /usr/lib64/jvm/java-openjdk/bin/java > -Djetty.logs=/var/log/jetty -Djetty.home=/usr/local/jetty > -Djetty.base=/usr/local/etc/jetty/base -Djava.io.tmpdir=/tmp -jar > /usr/local/jetty/start.jar jetty.state=/usr/local/etc/jetty/run/jetty.state > jetty-logging.xml jetty-started.xml > > Jetty running pid=2444 > > It's running > > ps ax | grep jetty > 2444 ? Sl 0:02 /usr/lib64/jvm/java-openjdk/bin/java > -Djetty.logs=/var/log/jetty -Djetty.home=/usr/local/jetty > -Djetty.base=/usr/local/etc/jetty/base -Djava.io.tmpdir=/tmp -jar > /usr/local/jetty/start.jar jetty.state=/usr/local/etc/jetty/run/jetty.state > jetty-logging.xml jetty-started.xml start-log-file=/var/log/jetty/start.log > 3276 pts/1 S+ 0:00 grep --color=auto jetty > > I've setup deployment in > > cat /usr/local/etc/jetty/jetty-deploy.xml > <?xml version="1.0"?> > <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" > "http://www.eclipse.org/jetty/configure_9_0.dtd";> > <Configure id="Server" class="org.eclipse.jetty.server.Server"> > <Call name="addBean"> > <Arg> > <New id="DeploymentManager" > class="org.eclipse.jetty.deploy.DeploymentManager"> > <Set name="contexts"> > <Ref refid="Contexts" /> > </Set> > <Call name="setContextAttribute"> > > <Arg>org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern</Arg> > <Arg>.*/servlet-api-[^/]*\.jar$</Arg> > </Call> > > <Call id="webappprovider" name="addAppProvider"> > <Arg> > <New class="org.eclipse.jetty.deploy.providers.WebAppProvider"> > <Set name="monitoredDirName">/home/hanl/jetty_webapps</Set> > <Set name="defaultsDescriptor"><Property name="jetty.home" > default="." />/etc/webdefault.xml</Set> > <Set name="scanInterval">1</Set> > <Set name="extractWars">true</Set> > <Set name="configurationManager"> > <New > class="org.eclipse.jetty.deploy.PropertiesConfigurationManager" /> > </Set> > </New> > </Arg> > </Call> > </New> > </Arg> > </Call> > </Configure> > > where I've extracted the solr.war to > > tree -d /home/hanl/jetty_webapps > /home/hanl/jetty_webapps > └── [jetty 4096] solr > ├── [jetty 4096] css > │ └── [jetty 4096] styles > ├── [jetty 4096] img > │ ├── [jetty 4096] filetypes > │ └── [jetty 4096] ico > ├── [jetty 4096] js > │ ├── [jetty 4096] lib > │ └── [jetty 4096] scripts > ├── [jetty 4096] META-INF > ├── [jetty 4096] tpl > └── [jetty 4096] WEB-INF > └── [jetty 4096] lib > > 13 directories > > When I re-start jetty and nav to > > http://127.0.0.1:8080 > > I apparently don't find the solr app > > Error 404 - Not Found. > No context on this server matched or handled this request. > Contexts known to this server are: > > Powered by Jetty:// Java Web Server > > I've obviously misconfigured something. > > Appreciate any help figuring out what! > > hanlon
