anchor.diff:  allows developers to quickly deploy an A-MQ message broker in a hybrid
   cloud environment.
   
  -However, there are significant differences in supported configurations and 
  +However, there are significant differences in supported configurations and
   functionality in the JBoss A-MQ image
   compared to the regular release of JBoss A-MQ. Documentation for other
   JBoss A-MQ functionality not specific to the JBoss A-MQ xPaaS image can
  
positive.code: <!-- ##MESSAGING_SUBSYSTEM## -->
  ----
  
  * EAP pod serving requests before it joins cluster, some sessions reset
  after failure:
  https://issues.jboss.org/browse/CLOUD-161[https://issues.jboss.org/browse/CLOUD-161]
  +
  In a distributed web application deployed on an EAP image, a new
  container starts serving requests before it joins the cluster.
  +
  There are no known workarounds available at this stage for this issue.
  
  *EAP and JWS*
  
  * Database pool configurations should contain validation SQL setting:
  https://issues.jboss.org/browse/CLOUD-159[https://issues.jboss.org/browse/CLOUD-159]
  +
  In both EAP and JWS images, when restarting a crashed database instance,
  the connection pools contain stale connections.
  +
  To work around this issue, restart all instances in case of a database
  failure.
  
  *A-MQ*
  
  
negative.code: release of JBoss EAP. To learn about these differences, please read
  link:../using_images/xpaas_images/eap.html[this documentation].
  Documentation for other JBoss EAP functionality not specific to the
  JBoss EAP xPaaS image can be found in the
  https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/[JBoss EAP documentation on the Red Hat Customer Portal].
  
  === xPaaS Image for Red Hat JWS
  