anchor.diff:  [[the-request-controller-subsystem]]
   == The Request Controller Subsystem
   
  -Wildfly introduces a new subsystem called the Request Controller
  +WildFly introduces a new subsystem called the Request Controller
   Subsystem. This optional subsystem tracks all requests at their entry
  -point, which how the graceful shutdown mechanism know when all requests
  -are done (it also allows you to provide a global limit on the total
  +point, which is how the graceful shutdown mechanism knows when all requests
  +are done. (It also allows you to provide a global limit on the total
   number of running requests).
   
  -If this subsystem is not present suspend/resume will be limited, in
  +If this subsystem is not present suspend/resume will be limited. In
   general things that happen in the PRE_SUSPEND phase will work as normal
  -(stopping message delivery, notifying the load balancer), however the
  -server will not wait for all requests to complete and instead move
  +(stopping message delivery, notifying the load balancer); however the
  +server will not wait for all requests to complete and instead will move
   straight to SUSPENDED mode.
   
   There is a small performance penalty associated with the request
  
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: 
  Returns the current suspend state of the server.
  
  `shutdown --timeout=x`
  
  If a timeout parameter is passed to the shutdown command then a graceful
  shutdown will be performed. The server will be suspended, and will wait
  in SUSPENDING state up to the specified number of seconds for all requests 
  to finish before shutting down. A timeout value of less than zero means 
  it will wait indefinitely.
  
  [[domain-mode]]
  == Domain Mode
  
  Domain mode has similar operations as standalone mode, however they can be
  applied at both the global and server group levels:
  
  *Whole Domain*
  
  `:suspend-servers(timeout=x)`
  
  `:resume-servers`
  
  `:stop-servers(timeout=x)`
  
  *Server Group*
  
  