# ElasticSearch Java API re-connect

**URL:** <https://discuss.elastic.co/t/elasticsearch-java-api-re-connect/177620>\
**Category:** Elasticsearch\
**Created:** [April 19, 2019, 1:06pm UTC](https://discuss.elastic.co/t/elasticsearch-java-api-re-connect/177620 "2019-04-19T13:06:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GUBENDRAN\_LAKSHMANAN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gubendran_lakshmanan/32/41950_2.png) [@GUBENDRAN\_LAKSHMANAN](https://discuss.elastic.co/u/GUBENDRAN_LAKSHMANAN)\
**Post date:** [April 19, 2019, 1:06pm UTC](https://discuss.elastic.co/t/elasticsearch-java-api-re-connect/177620/1 "2019-04-19T13:06:28Z")

</div>

We are having springboot application with yaml configuration configured with ElasticSEarch URL. In our application we started getting error "Caused by: org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: " when elasticsearch went to 'Red' or not available in the springboot code.

Once elasticSearch is back normal upon reboot still our application throws error "Caused by: org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: ". After restart web application error goes away. Is there a way we can force java to reconnect without restarting our web application ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 17, 2019, 1:06pm UTC](https://discuss.elastic.co/t/elasticsearch-java-api-re-connect/177620/2 "2019-05-17T13:06:29Z")

</div>

Closed on May 17, 2019, 1:06pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.