It's possible this may have changed in a recent release, and I don't
know about it, but when I last checked, the only information you could
get out of solrj was a SolrServerException with some very limited info -
basically - an error occurred on the server, and maybe HTTP 400.
When you say you
On 1/6/2012 3:57 PM, Michael Sokolov wrote:
See SOLR-141; there are a few patches - currently all you get back is
a 400 error with no actual information equivalent to what is logged in
the solr exception.
If I can get the HTTP code and the text that's in the error you see in
the browser, that
See SOLR-141; there are a few patches - currently all you get back is a
400 error with no actual information equivalent to what is logged in the
solr exception.
On 1/6/2012 12:46 PM, Shawn Heisey wrote:
On 1/5/2012 7:25 AM, Erick Erickson wrote:
Somewhere you have access to a CommonsHttpSolrS
On 1/5/2012 7:25 AM, Erick Erickson wrote:
Somewhere you have access to a CommonsHttpSolrServer, right? There's a
getHttpClient call that returns an org.apache.commons.httpclient that
might get you the information you need.
If I have a multithreaded app that shares a single HttpClient between
Shawn:
Somewhere you have access to a CommonsHttpSolrServer, right? There's a
getHttpClient call that returns an org.apache.commons.httpclient that
might get you the information you need.
Best
Erick
On Wed, Jan 4, 2012 at 1:03 PM, Shawn Heisey wrote:
> When doing Solr queries in a browser, it's
When doing Solr queries in a browser, it's pretty easy to see an HTTP
error status and read the reason, but I would like to do the same thing
in a deterministic way with SolrJ. Can anyone point me to examples that
show how to retrieve the HTTP status code and the reason for the error?
I would
