anchor.diff:  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 
  +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
  
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: 
  *JWS*
  
  * https://issues.jboss.org/browse/CLOUD-57[https://issues.jboss.org/browse/CLOUD-57]: Tomcat's access log valve logs to file in container instead of
  stdout
  +
  Due to this issue, the logging data is not available for the central logging
  facility. To work around this issue, use the `oc exec` command to get the
  contents of the log file.
  
  * https://issues.jboss.org/browse/CLOUD-153[https://issues.jboss.org/browse/CLOUD-153]: `mvn clean` in JWS STI can fail
  +
  It is not possible to clean up after a build in JWS STI because the Maven
  command `mvn clean` fails. This command fails due to Maven not being able to
  build the object model during startup.
  +
  To work around this issue, add Red Hat and JBoss repositories into the
  *_pom.xml_* file of the application if the application uses dependencies from
  there.
  
  * https://issues.jboss.org/browse/CLOUD-156[https://issues.jboss.org/browse/CLOUD-156]: Datasource realm configuration is incorrect for JWS
  +
  It is not possible to do correct JNDI lookup for datasources in the current JWS
  image if an invalid combination of datasource and realm properties is defined.
  If a datasource is configured in the *_context.xml_* file and a realm in the
  *_server.xml_* file, then the *_server.xml_* file's `*localDataSource*` property
  should be set to *true*.
  
  *EAP*
  
  * https://issues.jboss.org/browse/CLOUD-61[https://issues.jboss.org/browse/CLOUD-61]: JPA application fails to start when the database is not available
  +
  JPA applications fail to deploy in the EAP OpenShift Enterprise 3.0 image if an
  underlying database instance that the EAP instance relies on is not available at
  the start of the deployment. The EAP application tries to contact the database
  for initialization, but because it is not available, the server starts but the
  application fails to deploy.
  +
  There are no known workarounds available at this stage for this issue.
  
  * https://issues.jboss.org/browse/CLOUD-158[https://issues.jboss.org/browse/CLOUD-158]: Continuous HornetQ errors after scale down "Failed to create netty
  connection"
  +
  In the EAP image, an application not using messaging complains about messaging
  errors related to HornetQ when being scaled.
  +
  Since there are no configuration options to disable messaging to work around
  this issue, simply include the *_standalone-openshift.xml_* file within the
  source of the image and remove or alter the following lines related to
  messaging:
  +
  ----
  Line 18:
  