How to prevent HTTP 404 during deployment of ear i

问题:

We're using WildFly 10 as our application server and deploy via Docker (deployment in WF is ordinary hotdeployment). We're not using WildFly's clustering mechanisms but simply have load-balancers (HAProxys) in front.

The problem is that WF opens its HTTP port while the EAR deployment is still in progress. This (of course?) leads to HTTP 404 errors which we don't want to handle specifically in the LBs. This could lead to false negatives...

Is there a way to allow HTTP connections only after the EAR has started successfully?

Alternatively is it possible to replace the "404 because nothing is deployed here"-error with a "503 service unavailable"? This would much better express the problem and would be easy to handle externally...

回答1:

You can set default-response-code for host you are running this on.

something along the lines:

<host name="default-host" alias="localhost" default-response-code="503">

or in cli:

/subsystem=undertow/server=default-server/host=default-host:write-attribute(name=default-response-code, value=503)

and similarly for any other host you might have.