# Elasticsearch Java Transport Client - Max Connections

**URL:** <https://discuss.elastic.co/t/elasticsearch-java-transport-client-max-connections/26889>\
**Category:** Elasticsearch\
**Created:** [August 5, 2015, 12:49pm UTC](https://discuss.elastic.co/t/elasticsearch-java-transport-client-max-connections/26889 "2015-08-05T12:49:06Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Kiran\_Sriharsha](https://avatars.discourse-cdn.com/v4/letter/k/e36b37/32.png) [@Kiran\_Sriharsha](https://discuss.elastic.co/u/Kiran_Sriharsha)\
**Post date:** [August 10, 2015, 3:31am UTC](https://discuss.elastic.co/t/elasticsearch-java-transport-client-max-connections/26889/5 "2015-08-10T03:31:58Z")

</div>

I see only NoNodeAvailableException only in both ES and ES-Client logs.

We have made few experiments and identified that AWS LB was creating few issues that was closing connections. A question related to which is posted in [ES in AWS](https://discuss.elastic.co/t/es-in-aws/27086)

Thanks  
Sri Harsha

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-java-transport-client-max-connections/26889)._