Ending all TCP connections on a port -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Ending all TCP connections on a port
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Fri, 26 Jun 2020 10:55:50 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

We've had cases, on customer boxes, where a Tomcat stop-and-restart fails because of dangling connections.

I've been looking at ENDTCPCNN, but it appears to only work on one specific connection, Does anybody know of anything that can wipe out *all* connections for a given port, in one swell foop?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Ending all TCP connections on a port , Bryan Dietz
Re: Ending all TCP connections on a port , Kevin Bucknum

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.