[
https://issues.apache.org/jira/browse/SOLR-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840368#comment-13840368
]
Shawn Heisey commented on SOLR-5532:
------------------------------------
Got the example 4.6 server set up. With the following code, substantially
similar to yours, I do *NOT* get the same problem.
{code}
try
{
HttpSolrServer solrServer = new HttpSolrServer(
"http://localhost:8983/solr/collection1";);
SolrPingResponse x = solrServer.ping();
System.out.println(x);
}
catch (Exception e)
{
e.printStackTrace();
}
{code}
If I change "collection1" to "collection" (so the URL is invalid) then I do get
a similar (but not exactly the same) message, but it's part of a much larger
error. Can you help me figure out what I might be doing that's different from
your setup?
{noformat}
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Expected
content type application/octet-stream but got text/html;charset=ISO-8859-1.
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 404 Not Found</title>
</head>
<body><h2>HTTP ERROR 404</h2>
<p>Problem accessing /solr/collection/admin/ping. Reason:
<pre> Not Found</pre></p><hr /><i><small>Powered by
Jetty://</small></i><br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
</body>
</html>
at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:455)
at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:197)
at
org.apache.solr.client.solrj.request.SolrPing.process(SolrPing.java:69)
at org.apache.solr.client.solrj.SolrServer.ping(SolrServer.java:293)
at org.elyograg.TestStuff.main(TestStuff.java:72)
{noformat}
> HttpSolrServer does not accept content type of "ping" response
> --------------------------------------------------------------
>
> Key: SOLR-5532
> URL: https://issues.apache.org/jira/browse/SOLR-5532
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 4.6
> Environment: Windows 7, Java 1.7.0_45 (64bit), solr-solrj-4.6.0.jar
> Reporter: Jakob Furrer
>
> I just upgraded my Solr instance and with it I also upgraded the solrj
> library in our custom application which sends diverse requests and queries to
> Solr.
> I use the "ping" method to determine whether Solr started correctly under the
> configured address. Since the upgrade the ping response results in an error:
> {code:xml}
> Cause: org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:
> Expected content type application/xml; charset=UTF-8 but got
> application/xml;charset=UTF-8.
> <?xml version="1.0" encoding="UTF-8"?>
> <response>
> <lst name="responseHeader"><int name="status">0</int><int
> name="QTime">0</int><lst name="params"><str name="df">searchtext</str><str
> name="echoParams">all</str><str name="rows">10</str><str
> name="echoParams">all</str><str name="wt">xml</str><str
> name="version">2.2</str><str name="q">solrpingquery</str><str
> name="distrib">false</str></lst></lst><str name="status">OK</str>
> </response>
> {code}
> The Solr application itself works fine.
> Using an older version of the solrj library than solr-solrj-4.6.0.jar (e.g.
> solr-solrj-4.5.1.jar) in the custom application does not produce this error.
> The Exception is produced in a Code block (_HttpSolrServer.java_, method
> _request(...)_, around. line 140) which has been introduced with version
> 4.6.0.
> Code to reproduce the error:
> {code:xml}
> try {
> HttpSolrServer solrServer = new
> HttpSolrServer("my-solr-application-address");
> solrServer.ping();
> } catch (Exception e) {
> e.printStackTrace();
> }
> }
> {code}
> A global search for "charset=UTF-8" on the source code of solrj indicates
> that other functions besides "ping" might be affected as well, because there
> are several places where "application/xml; charset=UTF-8" is spelled without
> a space after the semicolon.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
