1 of 1 people found this helpful
We run Apache fronting WildFly with AJP. Apache will direct requests to WildFly as soon as Undertow Starts listening as well. We get 500 and 503 error responses depending on the time of startup processing. Even the HTTP listener will cause the same issues.
I was going to ask if you found a solution but I found the following and thought others may have the same problems and can save them some time:
Coming in WildFly 11
Unless there really is some work around for WildFly 10 this is a show stopper for the project I am on at least.
The graceful startup feature may indeed solve this problem - At some point, I intend to try this out, and I'll post the results of any investigation
This issue was one of the primary motivations for the mod_cluster project. The mod_cluster load balancer is application lifecycle aware such that availability of a web application is determined per deployment rather than based on a monolithic assumption about an open socket. This prevents not just 500/503 errors during server startup/shutdown, but also 404 errors following undeploy of a single application.
Undertow can even be configured to behave as a mod_cluster reverse proxy (I realize the names are confusing, we're working on it...) using standalone-load-balancer.xml.