# TransportClientNodeService onFailure stack over flow

**URL:** <https://discuss.elastic.co/t/transportclientnodeservice-onfailure-stack-over-flow/9400>\
**Category:** Elasticsearch\
**Created:** [October 18, 2012, 3:16am UTC](https://discuss.elastic.co/t/transportclientnodeservice-onfailure-stack-over-flow/9400 "2012-10-18T03:16:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jae/32/791_2.png) [@Jae](https://discuss.elastic.co/u/Jae)\
**Post date:** [October 18, 2012, 3:16am UTC](https://discuss.elastic.co/t/transportclientnodeservice-onfailure-stack-over-flow/9400/1 "2012-10-18T03:16:52Z")

</div>

Unfortunately, my elasticsearch instance was down due to unidentified  
reason. Much more unfortunately, our data pipeline also went down wholly  
because of OOM error.

It's not easy to reproduce but I just want to let elasticsearch committee  
know TransportClient has some defects.

I was seeing the following messages in the stdout log. I didn't copy&paste  
the same message multiple times, these lines were in the log file.

```
    at 

```

org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)  
at  
org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)  
at  
org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)  
at  
org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)  
at  
org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)  
at  
org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)  
at  
org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)  
at  
org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)  
at  
org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)  
at  
org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:252)

So, if I want to escape from TransportClient and change to HTTP client, is  
there any convenient way to transform messages into elasticsearch API json  
message? I tried to read RequestBuilder but it's not easy.

Thank you  
Best, Jae

--

---

<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, 3:08am UTC](https://discuss.elastic.co/t/transportclientnodeservice-onfailure-stack-over-flow/9400/2 "2017-07-06T03:08:13Z")

</div>