# Logstash with TCP input, TCP connection leak

**URL:** <https://discuss.elastic.co/t/logstash-with-tcp-input-tcp-connection-leak/207032>\
**Category:** Logstash\
**Created:** [November 8, 2019, 2:43am UTC](https://discuss.elastic.co/t/logstash-with-tcp-input-tcp-connection-leak/207032 "2019-11-08T02:43:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fawlk](https://avatars.discourse-cdn.com/v4/letter/f/43a26b/32.png) [@Fawlk](https://discuss.elastic.co/u/Fawlk)\
**Post date:** [November 8, 2019, 2:43am UTC](https://discuss.elastic.co/t/logstash-with-tcp-input-tcp-connection-leak/207032/1 "2019-11-08T02:43:14Z")

</div>

I have setup Logstash to receive log via TCP with only one client sending logs. After run for a while, I found that TCP Established connections and never timeout. After googled, there's a parameter data\_timeout that I could set TCP timeout but this parameters was removed since release 6.0.0. Could anyone advise about the configuration that could solve this issue?

---

<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:** [December 6, 2019, 2:43am UTC](https://discuss.elastic.co/t/logstash-with-tcp-input-tcp-connection-leak/207032/2 "2019-12-06T02:43:18Z")

</div>

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