# Jboss initiated client node not killed off in Elasticsearch 1.4.4

**URL:** <https://discuss.elastic.co/t/jboss-initiated-client-node-not-killed-off-in-elasticsearch-1-4-4/34436>\
**Category:** Elasticsearch\
**Created:** [November 12, 2015, 4:15pm UTC](https://discuss.elastic.co/t/jboss-initiated-client-node-not-killed-off-in-elasticsearch-1-4-4/34436 "2015-11-12T16:15:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nithyanand\_Vasudevan](https://avatars.discourse-cdn.com/v4/letter/n/278dde/32.png) [@Nithyanand\_Vasudevan](https://discuss.elastic.co/u/Nithyanand_Vasudevan)\
**Post date:** [November 12, 2015, 4:15pm UTC](https://discuss.elastic.co/t/jboss-initiated-client-node-not-killed-off-in-elasticsearch-1-4-4/34436/1 "2015-11-12T16:15:24Z")

</div>

Hi,

My web application is using an ES Node client. The ES server is a single node. Since we are in development stage, it was noticed that when we restarted JBoss for any reason the previous instance of ES Node client still appears in that ES server's cluster view.

Is there a time out that we can set?

What happens if I use multiple JBoss Instances in a cluster using the same cluster? Do the virtual client nodes then need to know each other as well?

---

<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 5, 2017, 11:38pm UTC](https://discuss.elastic.co/t/jboss-initiated-client-node-not-killed-off-in-elasticsearch-1-4-4/34436/2 "2017-07-05T23:38:55Z")

</div>

Closed on July 5, 2017, 11:38pm UTC