(27578908) When running on JBoss 7.0 EAP with a non-HA profile, the instance-id is not appended to the JSESSIONID cookie.
Due to an issue with JBoss 7.0, if you are using a non-HA profile, the instance-id is not automatically appended to the JSESSIONID cookie. To address this issue, CIM adds a jvmRoute filter to the profile’s XML configuration file when you assemble an application. This filter appends the instance-id to the JSESSIONID cookie. However, if you assemble the application using runAssembler rather than CIM, the filter is not added. In this case, follow the directions found here:

https://access.redhat.com/solutions/3140491

(25782972) Deployment fails on WebSphere Application Server 9 with StateChangeException.
There is a known issue with WebSphere Application Server 9 where an exception will occur when starting an application. This exception message is a service.state.StateChangeException. Refer to the IBM Support page for WebSphere for additional information.

Workaround: Add to custom JVM properties to the server to disable implicit bean scanning:

com.ibm.ws.cdi.enableImplicitBeanArchives=false
com.ibm.ws.cdi.enableDCI=false

(13301400) Inclusion of a welcome file on IBM WebSphere Application Server yields an error.
For example, a JSP that contains this dsp:include tag:

<dsp:include src="/" otherContext="/somecontext"/>

yields an error, as the dsp:include tag first flushes the response output stream, then WAS tries to resolve the welcome file by performing a forward, but the servlet spec prohibits performing a forward after output has been committed to the client.

Workaround: Specify the exact welcome file resource rather than just the directory.