The AS testsuite is encountering OOMEs during testing against the 'all' configuration.

The testsuite completes its run, and the problem is detected by noting that only 4022 of the 4103 tests in the testsuite have completed - the remainder have timed out due to an unresponsive server. Upon inspection of the server logs, the OOME messages are discovered.

I have attached the server.log and output.log from the AS server, as well as the test.log from the client side testsuite. These logs are not complete, as I terminated the testsuite run after noticing the error.

It is not clear which tests are causing the OOME. By looking at the timestamps on both logs, and noting that the first OOME occurred at 14:49:05 in the server log, this was at the time that the test org.jboss.test.jmx.test.RedeployStressTestCase was executing on the client side, but rerunning that test with a newly started AS did not reproduce the error.

I am planning to make a change to the AS testsuite so that before and after each test, the name of the test and the available heap space are printed out to the server log, so that a running view of memory use might help to track this down.