Server started with blocking=true times out only on a slave host

We use system property jboss.as.management.blocking.timeout for a slow starting server to avoid a timeout on startup. It works for a server on the master host-controller but doesn't work a server on a slave host.

Suppose a heavy application, for example, sleeping more than 300 seconds in ServletContext#contextInitialized(), is deployed and system property jboss.as.management.blocking.timeout is set in domain.xml to avoid timeout. Under the following domain configuration, server-one fails to start if blocking=true is specified.

• master
  • server-zero:start(blocking=true) => Success
• slave
  • server-one:start(blocking=true) => Fail

[domain@localhost:9990 /] /host=slave/server-config=server-one:start(blocking=true)
{
    "outcome" => "failed",
    "result" => undefined,
    "failure-description" => "WFLYCTL0409: Execution of operation 'start' on remote process at address '[(\"host\" => \"slave\")]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation",
    "rolled-back" => true
}