On 11/8/2012 3:25 PM, Dyer, James wrote:
Shawn,
Could this be a side-effect from SOLR-4019, in branch_4.0 this was commit r1405894 ?
Prior to this commit, PingRequestHandler would throw a SolrException for 503/Bad Request.
The change is that the exception isn't actually thrown but rather sent in place of the
response. This prevents the container from logging huge stack traces just because
PingrequestHandler is in a "disabled" state. Prior to this, SolrException had
logging disabled for 503's with hardcoding, but this broke other uses of 503 SE's.
My checkout of branch_4x is prior to the change from SOLR-4019. SolrJ is
considerably older, Solr is somewhat newer. I'm having a problem with
3.5.0 servers, not 4.x.
I'm already handling the exception when the ping handler is disabled and
returns a 503 error. The exception message is different between the two
versions, but I'm dealing with that. My problem happens when the ping
handler is enabled. Against a 4.1-SNAPSHOT server, I successfully get a
QueryResponse object from the query. Against a 3.5.0 server, I get an
exception, with this as the relevant piece:
Caused by: java.lang.RuntimeException: Invalid version (expected 2, but
60) or the data in not in 'javabin' format
at
org.apache.solr.common.util.JavaBinCodec.unmarshal(JavaBinCodec.java:109)
In a browser, using /solr/CORE/admin/ping gets me an XML response. For
both versions, in the main response section is a status field saying OK,
and in the responseHeader section is a status field with a value of zero.
I have not tried a SolrJ 3.5 against the 3.5 server. This program is
generating a status page for my entire Solr environment, both 3.5
production and 4.1 development, I can't run two versions.
Thanks,
Shawn
