This is resolved, I switched in the 4.2.1 jars and also corrected a mismatch
between the compile and runtime JDKs, for some reason the system was
overriding my JAVA_HOME setting (6.1) and running the client with a 5.0 JVM.
I did not have to use setParser.
I did try running the 'new' 4.2.1 SolrJ c
> I apologize for intruding, Shawn, do you know what can cause empty params
> (i.e. params={}) ?
I've got no idea what is causing this problem on your system. All of the
ideas I've had so far don't seem to apply.
Can you run a packet sniffer on your client to see whether the client is
sending the
I apologize for intruding, Shawn, do you know what can cause empty params
(i.e. params={}) ?
Ravi
On Mon, May 6, 2013 at 5:47 PM, Shawn Heisey wrote:
> On 5/6/2013 1:25 PM, cleardot wrote:
>
>> My SolrJ client uses ConcurrentUpdateSolrServer to index > 50Gs of docs
>> to a
>> SOLR 3.6 instance
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 setParse
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
On 5/6/2013 1:25 PM, cleardot wrote:
My SolrJ client uses ConcurrentUpdateSolrServer to index > 50Gs of docs to a
SOLR 3.6 instance on my Linux box. When running the same client against
SOLR 4.2.1 on EC2 I got the following:
SOLR 4.2.1 log error
=
