anchor.diff:  [[subsystem-integrations]]
   == Subsystem Integrations
   
  -Suspend/Resume is a service provided by the Wildfly platform that any
  +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
  +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
  +* *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
  
positive.code: server returns to running mode.
  * *EE Concurrency* - The server will wait for all active jobs to finish.
  All jobs that have already been queued will be skipped.
  * *Transactions* - transaction subsystem waits for all running
  transactions to finish while server is suspending. During that time
  server refuses to start any new transaction. But any in-flight
  transaction will be serviced - e.g. it means that server accepts any
  incoming remote call which carries context of the transaction already
  started at the suspending server. +
  When you work with EJBs you have to enable the graceful shutdown
  functionality by setting attribute `enable-graceful-txn-shutdown` to
  `true`. +
  (at the `ejb3 subsystem` xml, for example): +
  `<enable-graceful-txn-shutdown value="false"/>` +
  By *default* graceful shutdown it's *disabled* for ejb subsystem. +
  The reason is that the behavior might be unwelcome in cluster
  environments, as the server notifies remote clients that the node is no
  longer available for remote calls only after the transactions are
  finished. During that brief window of time, the client of a cluster may
  send a new request to a node that is shutting down and will refuse the
  request because it is not related to an existing transaction. +
  If this attribute `enable-graceful-txn-shutdown` is set to `false`, we
  disable the graceful behavior and EJB clients will not attempt to invoke
  the node when it suspends, regardless of active transactions.
  
negative.code: [[standalone-mode]]
  == 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 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`
  
  