You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When quarkus.http.port=0 AND quarkus.management.port=0 are set to let both HTTP servers use dynamic ports for testing purposes, it can happen that application requests are handled by the management server and vice versa.
IIUC both HTTP servers share the same port and Vert.x will dispatch requests "round robin", which is not so good.
Describe the bug
When
quarkus.http.port=0
ANDquarkus.management.port=0
are set to let both HTTP servers use dynamic ports for testing purposes, it can happen that application requests are handled by the management server and vice versa.IIUC both HTTP servers share the same port and Vert.x will dispatch requests "round robin", which is not so good.
Related Zulip Discussion
Related issue to expose the real management HTTP endpoint: #35952
Commit with some changes to expose the real HTTP endpoint
/cc @cescoffier
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: