In a domain mode :suspend-servers command with a timeout parameter different than 0 executes two suspend operations for each server in the domain. It first executes a suspend with 0ms and later a suspend with the timeout specified.

I'm proposing this as a potential blocker because the first suspend call essentially means the timeout is meaningless. The server will wait indefinitely to suspend (which is the behavior for a 0 timeout.) The second call won't execute until the first one completes, and at that point the server will be suspended.

How to reproduce it:

[domain@localhost:9990 /] :suspend-servers(timeout=10)

Server log traces show:

[Server:server-one] 20:14:40,126 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 0ms timeout.
[Server:server-one] 20:14:40,135 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout.

Expected traces are:

[Server:server-one] 20:14:40,135 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000 ms timeout.