On 4/19/2013 12:55 PM, Ravi Solr wrote:
We are using Solr 3.6.2 single core ( both index and query on same machine)
and randomly the server fails to query correctly. If we query from the
admin console the query is not even applied and it returns numFound count
equal to total docs in the index as if no query is made, and if use SOLRJ
to query it throws javabin error
Invalid version (expected 2, but 60) or the data in not in 'javabin' format
The UI problem is likely a browser issue, but I could be wrong. Some
browsers, IE in particular, but not limited to that one, have problems
with the admin UI. Using a different browser or clearing the browser
cache can sometimes fix those problems.
As for SolrJ, are you using a really old (1.x) SolrJ with Solr 3.6.2?
Have you ever had Solr 1.x running on the same machine that's now
running 3.6.2?
Because the javabin version changed between 1.4.1 and 3.1.0, SolrJ 1.x
is not compatible with Solr 3.1 and later unless you set the response
parser on the server object to XML before you try to use it. If you
have upgraded Solr from an old version, your servlet container
(sun-appserver) may have some of the old jars remaining from the 1.x
install. They must be removed.
To change your SolrJ to use the XML response parser, use code like the
following:
server.setParser(new XMLResponseParser());
When SolrJ and Solr are both version 3.x or 4.x, you can remove this line.
Another way that you can get the javabin error is when Solr is returning
an error response, or returning a response that is not an error but is
an HTML response reporting an unusual circumstance rather than the usual
javabin. These HTML responses should no longer exist in the newest
versions of Solr. Do you see any errors or warnings in your server log?
The server log line you included in your email is not an error.
Thanks,
Shawn
