# TCP output not working well **URL:** \ **Category:** Logstash\ **Created:** [March 21, 2016, 10:51am UTC](https://discuss.elastic.co/t/tcp-output-not-working-well/44974 "2016-03-21T10:51:04Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![StavSap](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StavSap](https://discuss.elastic.co/u/StavSap)\ **Post date:** [March 21, 2016, 10:51am UTC](https://discuss.elastic.co/t/tcp-output-not-working-well/44974/1 "2016-03-21T10:51:04Z")
i am outputting to a simple tcp server that accepts connection on port X and displays out comes to stdout, and in logstash i am outputting to port X on the address where is the server and to local stdout. the issue is this, when i send Y logs to logstash, i receive Y logs after parsing in the server. but if i send again, noting comes to the server, but i can see also in local stdout that log stash parsed the input. i have shut down the server and brought it up again, and then i saw the other parsed logs received. this behaviour suggest that log stash makes new tcp session after certain log parsing session. so i need to reaccept a new connection in the server. any one have a fix for this kind of behaviour? ---
**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:06am UTC](https://discuss.elastic.co/t/tcp-output-not-working-well/44974/2 "2017-07-06T05:06:08Z")