Agreed with Doug
On 12-Nov-2013 6:46 PM, "Doug Turnbull" <dturnb...@opensourceconnections.com>
wrote:

> As an aside, I think one reason people feel compelled to deviate from the
> distributed jetty distribution is because the folder is named "example".
> I've had to explain to a few clients that this is a bit of a misnomer. The
> IT dept especially sees "example" and feels uncomfortable using that as a
> starting point for a jetty install. I wish it was called "default" or "bin"
> or something where its more obviously the default jetty distribution of
> Solr.
>
>
> On Tue, Nov 12, 2013 at 7:06 AM, Roland Everaert <reveatw...@gmail.com
> >wrote:
>
> > In my case, the first time I had to deploy and configure solr on tomcat
> > (and jboss) it was a requirement to reuse as much as possible the
> > application/web server already in place. The next deployment I also use
> > tomcat, because I was used to deploy on tomcat and I don't know jetty at
> > all.
> >
> > I could ask the same question with regard to jetty. Why use/bundle(/ if
> not
> > recommend) jetty with solr over other webserver solutions?
> >
> > Regards,
> >
> >
> > Roland Everaert.
> >
> >
> >
> > On Tue, Nov 12, 2013 at 12:33 PM, Alvaro Cabrerizo <topor...@gmail.com
> > >wrote:
> >
> > > In my case, the selection of the servlet container has never been a
> hard
> > > requirement. I mean, some customers provide us a virtual machine
> > configured
> > > with java/tomcat , others have a tomcat installed and want to share it
> > with
> > > solr, others prefer jetty because their sysadmins are used to configure
> > > it...  At least in the projects I've been working in, the selection of
> > the
> > > servlet engine has not been a key factor in the project success.
> > >
> > > Regards.
> > >
> > >
> > > On Tue, Nov 12, 2013 at 12:11 PM, Andre Bois-Crettez
> > > <andre.b...@kelkoo.com>wrote:
> > >
> > > > We are using Solr running on Tomcat.
> > > >
> > > > I think the top reasons for us are :
> > > >  - we already have nagios monitoring plugins for tomcat that trace
> > > > queries ok/error, http codes / response time etc in access logs,
> number
> > > > of threads, jvm memory usage etc
> > > >  - start, stop, watchdogs, logs : we also use our standard tools for
> > that
> > > >  - what about security filters ? Is that possible with jetty ?
> > > >
> > > > André
> > > >
> > > >
> > > > On 11/12/2013 04:54 AM, Alexandre Rafalovitch wrote:
> > > >
> > > >> Hello,
> > > >>
> > > >> I keep seeing here and on Stack Overflow people trying to deploy
> Solr
> > to
> > > >> Tomcat. We don't usually ask why, just help when where we can.
> > > >>
> > > >> But the question happens often enough that I am curious. What is the
> > > >> actual
> > > >> business case. Is that because Tomcat is well known? Is it because
> > other
> > > >> apps are running under Tomcat and it is ops' requirement? Is it
> > because
> > > >> Tomcat gives something - to Solr - that Jetty does not?
> > > >>
> > > >> It might be useful to know. Especially, since Solr team is
> considering
> > > >> making the server part into a black box component. What use cases
> will
> > > >> that
> > > >> break?
> > > >>
> > > >> So, if somebody runs Solr under Tomcat (or needed to and gave up),
> > let's
> > > >> use this thread to collect this knowledge.
> > > >>
> > > >> Regards,
> > > >>     Alex.
> > > >> Personal website: http://www.outerthoughts.com/
> > > >> LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch
> > > >> - Time is the quality of nature that keeps events from happening all
> > at
> > > >> once. Lately, it doesn't seem to be working.  (Anonymous  - via GTD
> > > book)
> > > >>
> > > >> --
> > > >> André Bois-Crettez
> > > >>
> > > >> Software Architect
> > > >> Search Developer
> > > >> http://www.kelkoo.com/
> > > >>
> > > >
> > > > Kelkoo SAS
> > > > Société par Actions Simplifiée
> > > > Au capital de € 4.168.964,30
> > > > Siège social : 8, rue du Sentier 75002 Paris
> > > > 425 093 069 RCS Paris
> > > >
> > > > Ce message et les pièces jointes sont confidentiels et établis à
> > > > l'attention exclusive de leurs destinataires. Si vous n'êtes pas le
> > > > destinataire de ce message, merci de le détruire et d'en avertir
> > > > l'expéditeur.
> > > >
> > >
> >
>
>
>
> --
> Doug Turnbull
> Search & Big Data Architect
> OpenSource Connections <http://o19s.com>
>

Reply via email to