Can't get 1.2 running under Tomcat 5.5

Hi,

I'm having no luck getting Solr 1.2 to run under Tomcat 5.5
using  
context fragments. I've followed the example on wiki:
http://wiki.ap
ache.org/solr/SolrTomcat

The only thing I've changed is the installation method. I'm
using the  
Tomcat manager to create a context path, and also point to
my context  
config. This worked fine with Solr 1.1. If I tail the Tomcat
log  
(catalina.out) I get this (among other things):

java.lang.ArrayIndexOutOfBoundsException

Solr does create the data/index directory though along with
a few  
index files.

Anyone have any ideas as to what I could be doing wrong?

Thanks,
Matt

OK found the start of the trail... I had a duplicate entry
for  
fulltext in my schema. Removed that. Now when I first try to
deploy  
Solr, I get this error:

SEVERE: org.apache.solr.common.SolrException: Error loading
class  
'solr.IndexInfoRequestHandler'

Matt

On Sep 5, 2007, at 11:25 AM, Matt Mitchell wrote:

> Hi,
>
> I'm having no luck getting Solr 1.2 to run under Tomcat
5.5 using  
> context fragments. I've followed the example on wiki:
> http://wiki.ap
ache.org/solr/SolrTomcat
>
> The only thing I've changed is the installation method.
I'm using  
> the Tomcat manager to create a context path, and also
point to my  
> context config. This worked fine with Solr 1.1. If I
tail the  
> Tomcat log (catalina.out) I get this (among other
things):
>
> java.lang.ArrayIndexOutOfBoundsException
>
> Solr does create the data/index directory though along
with a few  
> index files.
>
> Anyone have any ideas as to what I could be doing
wrong?
>
> Thanks,
> Matt

Matt Mitchell
Digital Scholarship Services
Box 400129
Alderman Library
University of Virginia
Charlottesville, VA 22904

mwm4nvirginia.edu

: OK found the start of the trail... I had a duplicate entry
for fulltext in my
: schema. Removed that. Now when I first try to deploy Solr,
I get this error:

really? defining the same field name twice gave you an
ArrayIndexOutofBounds? ...  that's bad, i'll open a bug on
that.

: SEVERE: org.apache.solr.common.SolrException: Error
loading class
: 'solr.IndexInfoRequestHandler'

your solrconfig.xml seems to refer to
solr.IndexInfoRequestHandler ... 
this was a class that was added to the rcunk after Solr 1.1
was released, 
and was removed before 1.2 was released (all of it's
functionality was 
replaced by the LukeRequestHandler)




-Hoss

On Sep 5, 2007, at 11:37 AM, Matt Mitchell wrote:
> SEVERE: org.apache.solr.common.SolrException: Error
loading class  
> 'solr.IndexInfoRequestHandler'

You're using my old hand-built version of Solr, I suspect. 
Hoss  
explained it fully in his previous message on this thread.

Care needs to be taken when upgrading Solr but leaving
solrconfig.xml  
untouched because additional config may be necessary. 
Comparing your  
solrconfig.xml with the one that ships with the example app
of the  
version of Solr you're upgrading too is recommended.

	Erik

: Care needs to be taken when upgrading Solr but leaving
solrconfig.xml
: untouched because additional config may be necessary. 
Comparing your
: solrconfig.xml with the one that ships with the example
app of the version of
: Solr you're upgrading too is recommended.

Hmmm... that's kind of a scary statement, and it may
misslead people into 
thinking that they need to throw away their configs when
updating and 
start over with the newest examples -- that's certianly not
true.

I think it's safe to say that if you are using official
releases of Solr 
and not trunk builds, then either:
    * any "old" config files will continue to work
as is
OR: * any known config syntax which no longer works exactly
the same way 
      will be called out loudly in the CHANGES.txt files fo
the release.

If however you are using a nightly snapshot, items that work
in your 
config may not continue to work in future versions as
functionality is 
tweaked and revised.

However: Erik's point about comparing your configs with the
examples is 
still a good idea -- because their may be cool new features
that you'd 
like to take advantage of that dont immediately jump out at
you when 
looking at the CHANGES.txt file, but do when looking at
sample configs.



-Hoss

I guess my warning is more because I play on the edge and
have  
several times ended up tweaking various apps
solrconfig.xml's as I  
upgraded them to keep things working.

Anyway, we'll all agree that diff'ing your config files with
the  
example app can be useful.

	Erik

On Sep 5, 2007, at 9:26 PM, Chris Hostetter wrote:

>
> : Care needs to be taken when upgrading Solr but
leaving  
> solrconfig.xml
> : untouched because additional config may be necessary.
 Comparing  
> your
> : solrconfig.xml with the one that ships with the
example app of  
> the version of
> : Solr you're upgrading too is recommended.
>
> Hmmm... that's kind of a scary statement, and it may
misslead  
> people into
> thinking that they need to throw away their configs
when updating and
> start over with the newest examples -- that's certianly
not true.
>
> I think it's safe to say that if you are using official
releases of  
> Solr
> and not trunk builds, then either:
>     * any "old" config files will continue to
work as is
> OR: * any known config syntax which no longer works
exactly the  
> same way
>       will be called out loudly in the CHANGES.txt
files fo the  
> release.
>
> If however you are using a nightly snapshot, items that
work in your
> config may not continue to work in future versions as
functionality is
> tweaked and revised.
>
> However: Erik's point about comparing your configs with
the  
> examples is
> still a good idea -- because their may be cool new
features that you'd
> like to take advantage of that dont immediately jump
out at you when
> looking at the CHANGES.txt file, but do when looking at
sample  
> configs.
>
>
>
> -Hoss