Port bind skipped at server startup #19057
Labels
in:Transport
release bug
This bug is present in a released version of Open Liberty
release:210012
team:Sirius
Projects
Describe the bug
In an extremely rare scenario, configured ports can silently fail to bind - preventing Liberty from using them. This issue is caused by a subtle race condition in the code responsible for delaying the port bind until the server is ready to handle traffic.
In the failing scenario, the port started message will not be emitted - for example the following message will be missing:
and the following FFDC will be seen:
Steps to Reproduce
Configure one or more ports to start, for example:
And start the server. In this scenario, one or more of the ports will silently fail to bind.
Expected behavior
All configured ports should start, or if there is a problem some meaningful error message should be logged.
Diagnostic information:
IBM Semeru Runtime Open Edition (11.0.12+7)
The text was updated successfully, but these errors were encountered: