# TCP input miss data

**URL:** <https://discuss.elastic.co/t/tcp-input-miss-data/47678>\
**Category:** Logstash\
**Created:** [April 18, 2016, 4:14pm UTC](https://discuss.elastic.co/t/tcp-input-miss-data/47678 "2016-04-18T16:14:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kirill.krainov](https://avatars.discourse-cdn.com/v4/letter/k/a9a28c/32.png) [@kirill.krainov](https://discuss.elastic.co/u/kirill.krainov)\
**Post date:** [April 18, 2016, 4:14pm UTC](https://discuss.elastic.co/t/tcp-input-miss-data/47678/1 "2016-04-18T16:14:26Z")

</div>

I'm using tcp input to accept logs in json from other services. There is a bug, if you leave parameter -b default, and try send to socket 40-50k json logs w/o any timeouts, you will get a few invalid jsons and json parse error in logstash. Looks like tcp input don't finish with reading whole line till \n and concatenate it with the next one line till the next one \n

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 18, 2016, 9:50pm UTC](https://discuss.elastic.co/t/tcp-input-miss-data/47678/2 "2016-04-18T21:50:53Z")

</div>

Looks like you have also raised it here - [https://github.com/logstash-plugins/logstash-input-tcp/issues/51](https://github.com/logstash-plugins/logstash-input-tcp/issues/51)

---

<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, 5:01am UTC](https://discuss.elastic.co/t/tcp-input-miss-data/47678/3 "2017-07-06T05:01:44Z")

</div>