Thanks a lot, guys!! Alexandre's reply did the trick. Just changed
contexts/solr-jetty-context.xml.

On Fri Feb 06 2015 at 7:30:33 AM Walter Underwood <wun...@wunderwood.org>
wrote:

> Put Apache in front of it and rewrite all the URLs.
>
> wunder
> Walter Underwood
> wun...@wunderwood.org
> http://observer.wunderwood.org/
>
>
> On Feb 6, 2015, at 6:08 AM, Andrea Gazzarini <a.gazzar...@gmail.com>
> wrote:
>
> > Sorry I didn't read your email carefully: the rename workaround doesn't
> work if you want to publish a webapp on "/"
> >
> > On 02/06/2015 02:51 PM, Andrea Gazzarini wrote:
> >> That config parameter is within the <solrCloud> section while you are
> talking about a standalone server.
> >> The context root of a webapp is not something you can configure within
> the webapp itself, each server has is own way to do that.
> >>
> >> The simplest (but definitely no "elegant") way is to rename the
> solr.war under your deployment directory; this works with many servlet
> engines / application server - Jetty, Tomcat, JBoss, Weblogic, Websphere
> (most probably also with the others)
> >>
> >> On 02/06/2015 02:15 PM, Avanish Raju wrote:
> >>> I want to serve solr as a standalone server on a specific port, and
> need to
> >>> change the contextRoot from /solr to /
> >>> (I need to include some health checks on / which I will add to the
> solr.war)
> >>>
> >>> I've tried changing my node1/solr/solr.xml's hostContext variable to
> >>> $(hostContext:) instead of $(hostContext:solr) but this didn't change
> >>> anything athttp://localhost:8983/solr/. And if I go to
> >>> http://localhost:8983/, I get the following error:
> >>>
> >>> Error 404 - Not Found. No context on this server matched or handled
> this
> >>> request. Contexts known to this server are: /solr --->
> >>> o.e.j.w.WebAppContext{/solr,file:/home/yaraju_gmail_com/
> solr-4.10.3/node1/solr-webapp/webapp/},/home/yaraju_gmail_
> com/solr-4.10.3/node1/webapps/solr.war
> >>>
> >>> What is the right way to do this?
> >>>
> >>> Thanks,
> >>> Avanish
> >>>
> >>
> >
>
>

Reply via email to