Hmmm. I now get the following errors when trying to access my Mini cluster over 
http:

09:13:19,611 WARN  ~ Exception causing close of session 0x0 due to 
java.io.IOException: Len error 1347375956
09:13:19,611 INFO  ~ Closed socket connection for client /127.0.0.1:23244 (no 
session established for client)


I have a working code in which I start up a mini cluster and use it with the 
SolrClient obtained from the code line  miniCluster.getSolrClient(). This works 
fine.
Then I tried stopping the code execution after the mini cluster was started up, 
and then tried the following cURL commands. They all give the same error  given 
above:

curl -v -i -X POST 127.0.0.1:23052/solr/admin/cores?action=status
curl -v -i -X POST http://127.0.0.1:23052/solr/admin/cores?action=status
curl -v -i -X POST localhost:23052/solr/admin/cores?action=status

cURL response is:

* About to connect() to 127.0.0.1 port 23052 (#0)
*   Trying 127.0.0.1...
* Adding handle: conn: 0x457530
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x457530) send_pipe: 1, recv_pipe: 0
* Connected to 127.0.0.1 (127.0.0.1) port 23052 (#0)
> POST /solr/admin/cores?action=status HTTP/1.1
> User-Agent: curl/7.33.0
> Host: 127.0.0.1:23052
> Accept: */*
>
* Empty reply from server
* Connection #0 to host 127.0.0.1 left intact
curl: (52) Empty reply from server


-----Original Message-----
From: Rohana Rajapakse [mailto:rohana.rajapa...@gossinteractive.com] 
Sent: 12 May 2016 15:31
To: solr-user@lucene.apache.org
Subject: RE: http request to MiniSolrCloudCluster

You are correct Alan. My cluster seems to have not started correctly. Debugging 
now...

Thanks

-----Original Message-----
From: Alan Woodward [mailto:a...@flax.co.uk] 
Sent: 12 May 2016 13:18
To: solr-user@lucene.apache.org
Subject: Re: http request to MiniSolrCloudCluster

Are you sure that the cluster is running properly?  Probably worth checking its 
logs to make sure Solr has started correctly?

Alan Woodward
www.flax.co.uk


On 12 May 2016, at 12:48, Rohana Rajapakse wrote:

> Wait.
> With correct port, curl says : "curl: (52) Empty reply from server"
> 
> 
> -----Original Message-----
> From: Alan Woodward [mailto:a...@flax.co.uk] 
> Sent: 12 May 2016 11:35
> To: solr-user@lucene.apache.org
> Subject: Re: http request to MiniSolrCloudCluster
> 
> Hi Rohana,
> 
> What error messages do you get from curl?  MiniSolrCloudCluster just runs 
> jetty, so you ought to be able to talk to it over HTTP.
> 
> Alan Woodward
> www.flax.co.uk
> 
> 
> On 12 May 2016, at 09:36, Rohana Rajapakse wrote:
> 
>> Hi,
>> 
>> Is it possible to make http requests (e.g. from cURL) to an active/running  
>> MiniSolrCloudCluster?
>> One of my existing projects use http requests to an EmbeddedSolrServer. Now 
>> I am migrating to Solr-6/7 and trying to use MiniSolrCloudCluster. I have 
>> got a MiniSolrCloudCluster up and running, but existing requests fails to 
>> talk to my MiniSolrCloudCluster  using the url 
>> http://127.0.0.1:6028/solr/minicluster.
>> Even the ping requests to this MiniSolrCloudCluster fails: 
>> http://127.0.0.1:6028/solr/minicluster/admin/ping?wt=json&distrib=true&indent=true
>> 
>> Can someone please shed some light on this please?
>> 
>> Rohana
>> 
>> 
>> Registered Office: 24 Darklake View, Estover, Plymouth, PL6 7TL.
>> Company Registration No: 3553908
>> 
>> This email contains proprietary information, some or all of which may be 
>> legally privileged. It is for the intended recipient only. If an addressing 
>> or transmission error has misdirected this email, please notify the author 
>> by replying to this email. If you are not the intended recipient you may not 
>> use, disclose, distribute, copy, print or rely on this email.
>> 
>> Email transmission cannot be guaranteed to be secure or error free, as 
>> information may be intercepted, corrupted, lost, destroyed, arrive late or 
>> incomplete or contain viruses. This email and any files attached to it have 
>> been checked with virus detection software before transmission. You should 
>> nonetheless carry out your own virus check before opening any attachment. 
>> GOSS Interactive Ltd accepts no liability for any loss or damage that may be 
>> caused by software viruses.
>> 
>> 
> 

Reply via email to