(13301400) Inclusion of a welcome file on WAS 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.

(13287159) runAssembler -run-in-place option no longer accesses WAR files in the ATG installation.
The runAssembler -run-in-place option now requires that any WAR files in an application be deployed to the JBoss directory structure, rather than being accessed directly from the ATG installation. This means that if you make changes to a WAR file in the ATG installation, those changes are no longer immediately available.

Workaround: To make your changes available, call runAssembler -run-in-place again, so that the modified WAR file is redeployed.

(13308044) JBoss 5.1.0 uses 100% CPU even if no user interface actions are performed; no server errors are logged. This behavior is due to a JBoss bug.

Workaround: See the following link for information and a workaround:

https://issues.jboss.org/browse/JBPAPP-5193