# No node available while exception caught on transport layer

**URL:** <https://discuss.elastic.co/t/no-node-available-while-exception-caught-on-transport-layer/14296>\
**Category:** Elasticsearch\
**Created:** [November 7, 2013, 12:51am UTC](https://discuss.elastic.co/t/no-node-available-while-exception-caught-on-transport-layer/14296 "2013-11-07T00:51:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![spancer\_ray](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spancer_ray/32/76303_2.png) [@spancer\_ray](https://discuss.elastic.co/u/spancer_ray)\
**Post date:** [November 7, 2013, 12:51am UTC](https://discuss.elastic.co/t/no-node-available-while-exception-caught-on-transport-layer/14296/1 "2013-11-07T00:51:50Z")

</div>

Hi guys,

I'm using java api (transportClient) to call remote es cluser to index data, and occasionally, a warn message 'exception caught on transport layer [id:xxx /localhost ip:serve port =\> /remote es host ip: port], cloing connection.' sent out.  
After this, a no node available exception throws out, then , my data can't be indexed to es cluster.

I generate the tansport client from a singleton class which init only once, and i'm sure it's not some es performance Issues, this only happens while doing a remote call, because whenever doing the same work in the local area network, it never happens. It was weird, anyone got an idea on this?

Thanks,  
Spancer

---

<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:** [July 6, 2017, 2:08am UTC](https://discuss.elastic.co/t/no-node-available-while-exception-caught-on-transport-layer/14296/2 "2017-07-06T02:08:26Z")

</div>