Hi
I've upgraded my solr server (a single core with single collection) from
4.3.1 to 4.4.0, using the new solr.xml
configuration file from example and setting the new core.properties (with my
collection name) under the instance dir.
When i check the status of solr via web interface, all is up and going
smoothly (it find the core with autodiscovery),
and i can query and get responses from the solr server.
When i try to access solr with an application that i wrote via solrj, using
the same parameter i was using for past version
it return an exception:
RemoteSolrException: Server at http://(my-server-address)/solr returned non
ok status:404, message:Not Found
Even a simple call of server.ping() return the same exception.
So i've changed my instance dir name as "collection1" and put the same value
on core.properties, restarted the solr server
and the application started to work again.
Is there someghing i'm missing? It's a strange behaviour because via web
interface everything is regularly, but
when i try to do some action via solrj with a custom core name it return an
exception.
Any help is appreciated! Thanks
This is my solr.xml
<solr>
<solrcloud>
<str name="host">${host:}</str>
<int name="hostPort">${jetty.port:8983}</int>
<str name="hostContext">${hostContext:solr}</str>
<int name="zkClientTimeout">${zkClientTimeout:15000}</int>
<bool name="genericCoreNodeNames">${genericCoreNodeNames:true}</bool>
</solrcloud>
<shardHandlerFactory name="shardHandlerFactory"
class="HttpShardHandlerFactory">
<int name="socketTimeout">${socketTimeout:0}</int>
<int name="connTimeout">${connTimeout:0}</int>
</shardHandlerFactory>
</solr>
And this is the only entry in core.properties, under the instance directory
(/opt/solr-4.4.0/example/solr/soccerevents):
name=soccerevents
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-4-0-and-solrj-tp4080282.html
Sent from the Solr - User mailing list archive at Nabble.com.
