On 5/6/2013 4:06 PM, cleardot wrote:
Shawn,

I didn't sanitize the log other than the ec2 servername.  The constructor is

        ConcurrentUpdateSolrServer solrServer
                          = new ConcurrentUpdateSolrServer(solrUrl,
solrBufferCount, solrThreadCount);

and I don't use setParser at all.

But the SolrJ client is using apache-solr-core-3.6.1.jar and
apache-solr-solrj-3.6.1.jar while the server is 4.2.1.  Maybe I do need to
use setParser?

The javabin versions between those two are compatible, but the older SolrJ may not send a content type when using javabin, and the newer Solr seems to require it. Perhaps if you do change the parser, it might force the issue. XML isn't quite as efficient as javabin, but it's not like it will be super slow either. Add the following after creating the server object:

solrServer.setParser (new XMLResponseParser());

This probably will require adding an import:

import org.apache.solr.client.solrj.impl.XMLResponseParser;

You also might try upgrading SolrJ on your client app. I'm using SolrJ 4.2.1 with two different server versions - 3.5.0 and 4.2.1. It works perfectly.

Thanks,
Shawn

Reply via email to