__
> From: Rallavagu
> Sent: Thursday, April 10, 2014 2:13 AM
> To: solr-user@lucene.apache.org
> Subject: Re: No route to host
>
> Sorry. I should have mentioned earlier. I have removed the original host
> name on purpose. Thanks.
>
> On
to check any configuration missing.
Thanks,
SureshKumar.S
From: Rallavagu
Sent: Thursday, April 10, 2014 2:13 AM
To: solr-user@lucene.apache.org
Subject: Re: No route to host
Sorry. I should have mentioned earlier. I have removed the original host
name
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.net.NoRouteToHostException: No route to host
at java.net.PlainSocketImpl.socketConnect(Native Method
g.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thr
Agreed. But, it is failing to find route to itself. Weird.
On 4/9/14, 1:34 PM, Greg Walters wrote:
This doesn't looks like a solr-specfic issue. Be sure to check your routes and
your firewall. I've seen firewalls refuse packets and return a special flag
that results in a no rou
This doesn't looks like a solr-specfic issue. Be sure to check your routes and
your firewall. I've seen firewalls refuse packets and return a special flag
that results in a no route to host error.
Thanks,
Greg
On Apr 9, 2014, at 3:28 PM, Rallavagu wrote:
> All,
>
> I see
by: java.net.NoRouteToHostException: No route to host
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at
