Skip to content

Fix some tcp brokenness#2336

Closed
eboasson wants to merge 7 commits intoeclipse-cyclonedds:masterfrom
eboasson:fix-some-tcp-brokenness
Closed

Fix some tcp brokenness#2336
eboasson wants to merge 7 commits intoeclipse-cyclonedds:masterfrom
eboasson:fix-some-tcp-brokenness

Conversation

@eboasson
Copy link
Contributor

... while leaving most of it in place.

The TCP support in Cyclone really never was any good, but it rotted to the point of not working well in various configurations. That is simply too much. This fixes a few things that make it work somewhat, but it doesn't fix the real problems.

@eboasson eboasson force-pushed the fix-some-tcp-brokenness branch from 518c6d6 to ea2b1f7 Compare January 20, 2026 10:03
Signed-off-by: Erik Boasson <eb@ilities.com>
No TCP server socket was created if the configured TCP port number is 0, instead of one
listening on a random port number.

Signed-off-by: Erik Boasson <eb@ilities.com>
Signed-off-by: Erik Boasson <eb@ilities.com>
Signed-off-by: Erik Boasson <eb@ilities.com>
We don't allocate server port numbers like we do with UDP, so adding them makes no sense.

Signed-off-by: Erik Boasson <eb@ilities.com>
Signed-off-by: Erik Boasson <eb@ilities.com>
There are a number of problems with the TCP implementation that are caused by a bad
design. The problems are various:

* ownership of connections
* handling of disconnects
* potential blocking at bad times

fixing the requires a wholesale rewrite. It does work reasonably well in somewhat benign
settings, and it has on occasion helped save the day. Disabling by default minimises the
risk while retaining something that people may have been using.

Signed-off-by: Erik Boasson <eb@ilities.com>
@eboasson eboasson force-pushed the fix-some-tcp-brokenness branch from ea2b1f7 to bfda591 Compare January 26, 2026 16:02
@eboasson eboasson closed this Feb 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant