Jack, the JNDI-enabling jarfiles now ship as part of the main .zip
distribution. There is no need for a separate JettyPlus download as
of Jetty 6.
I used Jetty 6.1.3 (http://dist.codehaus.org/jetty/jetty-6.1.x/
jetty-6.1.3.zip) at the time, and I am using only these jarfiles from
the main distribution. I stripped everything else out that seemed
unnecessary for running Solr.
lib/jetty-6.1.3.jar
lib/jetty-util-6.1.3.jar
lib/jsp-2.1/ant-1.6.5.jar
lib/jsp-2.1/core-3.1.1.jar
lib/jsp-2.1/jsp-2.1.jar
lib/jsp-2.1/jsp-api-2.1.jar
lib/naming/jetty-naming-6.1.3.jar
lib/plus/jetty-plus-6.1.3.jar
lib/servlet-api-2.5-6.1.3.jar
--Matt
On Sep 13, 2007, at 11:44 AM, Jack L wrote:
Thanks Matt, I'll give it a try! So this requires JettyPlus?
--
Best regards,
Jack
Wednesday, September 12, 2007, 5:14:32 AM, you wrote:
Jack, I've posted a complete recipe for running two Solr indices
within one Jetty 6 container:
http://wiki.apache.org/solr/SolrJetty
Scroll down to the part that says:
(7/2007 MattKangas) The recipe above didn't work for me with Jetty
6.1.3.
...
I'm glossing over a lot of details, so attached is a tarball with a
known-good configuration that runs two Solr instances inside one
Jetty container. I'm using Solr 1.2.0 and Jetty 6.1.3 respectively.
Hope this helps,
--matt
On Sep 11, 2007, at 11:52 AM, Jack L wrote:
I was going through some old emails on this topic. Rafael Rossini
figured
out how to run multiple indices on single instance of jetty but it
has to
be jetty plus. I guess jetty doesn't allow this? I suppose I can add
additional jars and make it work but I haven't tried that. It'll
always be much safer/simpler/less playing around if a feature is
available out of box.
I'm mentioning this again because I really think it's a desirable
feature,
especially because each JVM uses a lot of memory and sometimes it's
not possible to start a new jetty for each index due to memory
limitation.
I understand I can use a type field and mix doc types but this is
not
ideal for two reasons:
1. it's easier to maintain separate indices. I can just wipe out all
the files and re-post an individual index. Much less posting work to
do as opposed to re-posting all docs. Or I can move one index to
another partition, or even to another server to run separately in
order to scale up. It'll be a problem (although solvable by deleting
and re-posting) with a mixed index.
2. my understanding is that mixed index means larger index files and
slower performance
JettyPlus's download links seem to be broken so I wasn't able to
check
its download size. If not too big, maybe JettyPlus is an option?
If not, there should be a way to have this feature implemented on
solr
side? Maybe by prefixing the REST URLs with index names...
--
Thanks,
Jack
--
Matt Kangas / [EMAIL PROTECTED]
--
Matt Kangas / [EMAIL PROTECTED]
