# Transport client creates undefined conditions on server nodes

**URL:** <https://discuss.elastic.co/t/transport-client-creates-undefined-conditions-on-server-nodes/20553>\
**Category:** Elasticsearch\
**Created:** [November 4, 2014, 9:51am UTC](https://discuss.elastic.co/t/transport-client-creates-undefined-conditions-on-server-nodes/20553 "2014-11-04T09:51:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sven\_Jorns](https://avatars.discourse-cdn.com/v4/letter/s/ecd19e/32.png) [@Sven\_Jorns](https://discuss.elastic.co/u/Sven_Jorns)\
**Post date:** [November 4, 2014, 9:51am UTC](https://discuss.elastic.co/t/transport-client-creates-undefined-conditions-on-server-nodes/20553/1 "2014-11-04T09:51:09Z")

</div>

Hi,  
we use ES from a old jboss to connect to a new ES Server Cluster (2 Nodes)  
with a transport client.  
At this point (yes, should improved) we use java 6 with jboss, so we can  
use ES version 1.1.1 as client. We also use lucene in a jboss application  
with the same version uses with ES (4.7.2)  
Server nodes running under Java 7 with version 1.3.2 of ES.

Most of the time this combination work fine, but some time one server turns  
into undefined conditions. Connecting with the client seems to work  
(execute), but the ES Server don't give data (get). Also the timeout  
defined with client.transport.ping\_timeout have no influence to stop  
getting data. No errors in server log.

my hints of this problem:

- I have a wrong configuration of transport clients
- I have not all lucene jars, because I`m using only Transport Client
- there is a problem with closing (singleton) clients unsafe (many warnings  
like [2014-11-04 09:06:59,658][WARN][transport.netty] [svennb-1]  
exception caught on transport layer [[id: 0xec4e7db5, /172.16.12.217:61928  
=\> /172.16.12.217:9300]], closing connection ) in log file

Some more hints?

thanks,  
Sven

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/591142f8-b2c3-4d2a-a97b-55b8c1851cf7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/591142f8-b2c3-4d2a-a97b-55b8c1851cf7%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:52am UTC](https://discuss.elastic.co/t/transport-client-creates-undefined-conditions-on-server-nodes/20553/2 "2017-07-06T00:52:20Z")

</div>

Closed on July 6, 2017, 12:52am UTC