I gave few new shots today: - with jetty and nightly build 16 Jan - same problem null pointer exception - Then I decided I am not using solr multicore but rather tomcat to handle this. So I get latets tomcat and again with using 1.3.0 solr.war I setup all as explained http://wiki.apache.org/solr/SolrTomcat#head-024d7e11209030f1dbcac9974e55106abae837ac Links again are all smooth for admin and all but I still get 500 on pings :(
Is everyone using solr with single index(core) ? Cheers All setup is smooth, working Julian Davchev wrote: > Hi, > > I am trying with 1.3.0 from > http://apache.cbox.biz/lucene/solr/1.3.0/apache-solr-1.3.0.tgz > > which I supposed is stable release. > > Otis Gospodnetic wrote: > >> Not sure, I'd have to try it. But you didn't mention which version of Solr >> you are using. Nightly build? >> >> >> Otis >> -- >> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch >> >> >> >> ----- Original Message ---- >> >> >>> From: Julian Davchev <j...@drun.net> >>> To: solr-user@lucene.apache.org >>> Sent: Thursday, January 15, 2009 9:53:37 AM >>> Subject: Is it just me or multicore default is broken? Can't ping >>> >>> Hi, >>> I am trying to setup multicore solr. So I just download default one with >>> jetty.......goto example/ >>> and run >>> java -Dsolr.solr.home=multicore -jar start.jar >>> >>> >>> All looks smooth without errors on startup. >>> Also can can open admin at >>> >>> http://localhost:8983/solr/core1/admin/ >>> >>> >>> But then trying to ping >>> http://localhost:8983/solr/core1/admin/ping >>> >>> I get error 500 INTERNAL SERVER ERROR >>> >>> >>> And tons of exceptions in background starting with nullpointer >>> >>> Anyone have a clue? Is solr stable to be used or multicore is something >>> reacently added and not to be trusted yet? >>> >>> >> >> > >
