Hi Shawn,
I try to fix the problem with original jars and now just discovered it
happens only with SolrJ client when doing a soft commit with the
following method call signature:
solr.commit(false, false, true);
Where solr is an HttpSolrServer initialized at the beginning of the
application, the only way to make the error go away is by downgrading to
the SolrJ client to 4.9.0
Hope that helps,
Guido.
On 05/09/14 19:14, Shawn Heisey wrote:
On 9/5/2014 3:50 AM, Guido Medina wrote:
Sorry I didn't give enough information so I'm adding to it, the SolrJ
client is on our webapp and the documents are getting indexed properly
into Solr, the only problem we are seeing is that with SolrJ 4.10 once
Solr server response comes back it seems like SolrJ client doesn't know
what to with such response and reports the exception I mentioned, I then
downgraded the SolrJ client to 4.9 and the exception is now gone, I'm
using the following relevant libraries:
Java 7u67 64 bits at both webapp client side side and Jetty's
HTTP client/mine 4.3.5
HTTP core 4.3.2
Here is a list of my Solr war modified lib folder, I usually don't stay
with the standard jars because I believe most of them are out of date if
you are running a JDK 7u55+:
You're in uncharted territory if you're going to modify the jars
included with Solr itself. We do upgrade these from time to time, and
usually it's completely harmless, but we also run all the tests when we
do it, to make sure that nothing will get broken. Some of the
components are on specific versions because upgrading them isn't as
simple as simply changing the jar.
What happens if you return Solr to what's in the release war?
Thanks,
Shawn
