[ https://issues.jboss.org/browse/WFCORE-1467?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-1467: --------------------------------------- The issue with the timeout being doubled is because {{DomainServerLifecycleHandlers.SuspendServersLifecycleHandler}} calculates the millis and passes to the [{{ServerInventory.awaitServerSuspend()}}|https://github.com/wildfly/wildfly-core/blob/2.1.0.Final/host-controller/src/main/java/org/jboss/as/host/controller/ManagedServer.java#L711-L730] which executes {{suspend}} again with the timeout which is once again calculated on the suspend operation. This is the same reason we see the suspend twice actually. It happens first for [each server|https://github.com/wildfly/wildfly-core/blob/2.1.0.Final/host-cont...] then happens again in the {{ServerInventory.awaitServerSuspend()}}. {code:java} for (String serverName : processes.keySet()) { final String serverModelName = serverInventory.getProcessServerName(serverName); if (group == null || serversInGroup.contains(serverModelName)) { serverInventory.suspendServer(serverModelName); waitForServers.add(serverModelName); } } if (timeout != 0) { serverInventory.awaitServerSuspend(waitForServers, timeout > 0 ? timeout * 1000 : timeout); } {code} The double timeout is easy to fix. The actual suspend operation I'm not so sure what the correct approach is. [~brian.stansberry] what do you think? -- This message was sent by Atlassian JIRA (v6.4.11#64026)