# TCP output plugin blocking port on pipeline reload

**URL:** <https://discuss.elastic.co/t/tcp-output-plugin-blocking-port-on-pipeline-reload/373574>\
**Category:** Logstash\
**Created:** [January 23, 2025, 10:30am UTC](https://discuss.elastic.co/t/tcp-output-plugin-blocking-port-on-pipeline-reload/373574 "2025-01-23T10:30:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sidd](https://avatars.discourse-cdn.com/v4/letter/s/ba8739/32.png) [@Sidd](https://discuss.elastic.co/u/Sidd)\
**Post date:** [January 23, 2025, 10:30am UTC](https://discuss.elastic.co/t/tcp-output-plugin-blocking-port-on-pipeline-reload/373574/1 "2025-01-23T10:30:23Z")

</div>

On upgrading from logstash-oss-8.5.2-1 to 8.15.4 which started to use logstash-output-tcp Plugin version: v6.2.1 from Plugin version: v6.1.1. It seems the bug which was resolved as mentioned in changelog of 6.1.0 is introduced again for closing client sockets on pipeline reload-  
**6.1.0 Changelogs as**  
Feat: ssl\_supported\_protocols (TLSv1.3) #47  
Fix: close server and client sockets on plugin close

Can someone please help me identify why on reloading pipeline logstash does not release the output port ? If I stop the logstash service and start it again then everything works fine. I want same to happen with conf reload. Please help.