> Solr problem. You probably have some kind of system-level classpath > problem where the wrong version of a critical jar is being used instead > of the jar that's included with Jetty in the Solr download.
Since our bin/solr script starts Jetty using java -jar, any CLASSPATH environment variables are ignored, so the only place to mess things up would be if IBM VM somehow includes servlet-api 2.4 before Solr’s own 3.1 version. That’s why it would be interesting to try with Oracle Java. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com
