-
Notifications
You must be signed in to change notification settings - Fork 778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[20313] Allow single listening port on TCP #4348
Conversation
19ee370
to
2fd7a0e
Compare
07bfc00
to
b4a0291
Compare
2fd7a0e
to
17a6d47
Compare
17a6d47
to
2897ae3
Compare
Moved to 2.14, since this changes behavior |
@jepemi This has some conflicts that need to be resolved before reviewing |
2897ae3
to
6e11055
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with green CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix warnings on Windows (signed / unsigned comparisons in the test)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with green CI
@richiprosima please test this |
Although Jenkins Mac CI has not been run, Mac GitHub CI passes. |
@jepemi This is ready to merge, but I think a documentation PR describing the limitation is necessary |
… & fix fill unicast locators Signed-off-by: Jesus Perez <jesusperez@eprosima.com>
Signed-off-by: Jesus Perez <jesusperez@eprosima.com>
Signed-off-by: Jesus Perez <jesusperez@eprosima.com>
Signed-off-by: Jesus Perez <jesusperez@eprosima.com>
e20c1cc
to
cdf6c46
Compare
Description
When several listening ports are added to the TCP transport, the data communication does not work or, if it does, it is in an undesired way. Servers create an acceptor on each of the listening ports. Since the server locators sent in the discovery phase only include the first added listening port, clients connected to another of the listening ports never find the resource that their initial peer initially created and end up creating a new channel for the locators obtained from the discovery data. If this new resource manages to connect, a new thread is created on both sides.
This PR limits the amount of listening ports to one, which effectively will only create an acceptor on the first indicated listening port. If more listening ports are passed, those are ignored.
Contributor Checklist
versions.md
file (if applicable).Related documentation PR: [20313] Allow single listening port on TCP Fast-DDS-docs#717
Reviewer Checklist