# Endless stacktrace in log4j when using TransportClient

**URL:** <https://discuss.elastic.co/t/endless-stacktrace-in-log4j-when-using-transportclient/166674>\
**Category:** Elasticsearch\
**Created:** [February 1, 2019, 5:30am UTC](https://discuss.elastic.co/t/endless-stacktrace-in-log4j-when-using-transportclient/166674 "2019-02-01T05:30:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheLeap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theleap/32/42366_2.png) [@TheLeap](https://discuss.elastic.co/u/TheLeap)\
**Post date:** [February 1, 2019, 5:30am UTC](https://discuss.elastic.co/t/endless-stacktrace-in-log4j-when-using-transportclient/166674/1 "2019-02-01T05:30:14Z")

</div>

# [NoNodeAvailableException and endless stacktrace in log4j when using TransportClient](https://discuss.elastic.co/t/nonodeavailableexception-and-endless-stacktrace-in-log4j-when-using-transportclient/4823)

Is there any changes to this as I am still seeing these recursive log trace which is causing StackOverFlow error.

---

<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:** [March 1, 2019, 5:30am UTC](https://discuss.elastic.co/t/endless-stacktrace-in-log4j-when-using-transportclient/166674/2 "2019-03-01T05:30:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.