Navigation Menu

Skip to content
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

Fix the handling of the port 0 #12401

Merged
merged 1 commit into from Sep 29, 2020
Merged

Conversation

cescoffier
Copy link
Member

By updating the options object, it create a race conditions.
One verticle may be already listening and would have updated the port in the HTTP option.
So, the next verticle see this set port (no more 0) and try to bind on that port, which lead to a BindException.

This commit stores the actual HTTP and HTTPS port without modifying the HTTP options.

By updating the options object, it create a race conditions.
One verticle may be already listening and would have updated the port in the HTTP option.
So, the next verticle see this set port (no more 0) and try to bind on that port, which lead to a BindException.

This commit stores the actual HTTP and HTTPS port without modifying the HTTP options.
@cescoffier cescoffier added kind/bug Something isn't working area/vertx labels Sep 29, 2020
@cescoffier cescoffier added this to the 1.9.0 - master milestone Sep 29, 2020
@cescoffier
Copy link
Member Author

@phillip-kruger That fixes the MQTT client issue :-)

@stuartwdouglas stuartwdouglas merged commit 4216d7a into quarkusio:master Sep 29, 2020
@gsmet gsmet modified the milestones: 1.9.0 - master, 1.8.2.Final Oct 1, 2020
@cescoffier cescoffier deleted the fix-port0 branch August 1, 2021 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vertx kind/bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants