anchor.diff:  [[standalone-mode]]
   == Standalone Mode
   
  -Suspend/Resume can be controlled via the following CLI operations in
  -standalone mode:
  +Suspend/Resume can be controlled via the following CLI operations 
  +and commands in standalone mode:
   
   `:suspend(timeout=z)`
   
  -Suspends the server. If the timeout is specified it will wait up to the
  -specified number of seconds for all requests to finish. If there is no
  -timeout specified or the value is less than zero it will wait
  -indefinitely.
  +Suspends the server. If the timeout is specified it will wait in the 
  +SUSPENDING phase up to the specified number of seconds for all requests
  +to finish. If there is no timeout specified or the value is less than 
  +zero it will wait indefinitely.
   
   `:resume`
   
  
positive.code: [[subsystem-integrations]]
  == Subsystem Integrations
  
  Suspend/Resume is a service provided by the Wildfly platform that any
  subsystem may choose to integrate with. Some subsystems integrate
  directly with the suspend controller, while others integrate through the
  request controller subsystem.
  
  The following subsystems support graceful shutdown. Note that only
  subsystems that provide an external entry point to the server need
  graceful shutdown support, for example the JAX-RS subsystem does not
  require suspend/resume support as all access to JAX-RS is through the
  web connector.
  
  * *Undertow* - Undertow will wait for all requests to finish
  * *mod_cluster* - The mod_cluster subsystem will notify the load
  balancer that the server is suspending in the PRE_SUSPEND phase.
  * *EJB* - EJB will wait for all remote EJB requests and MDB message
  
negative.code: 
  `/host=master/server-config=server-one:suspend(timeout=x)`
  
  `/host=master/server-config=server-one:resume`
  
  `/host=master/server-config=server-one:stop(timeout=x)`
  