Not really, other than looking in the server.log from the all config to see if it reveals anything. Last week I was testing with the clustering configs (called node0 and node1) and ant didn't have any problems stopping them on my dev machine. They're stripped down versions of 'all'. Only tangentially related, but the AS testsuite adds xmlns:server="http://jboss.org/ns/test/ant/server" to the "project" tag in its build xml and thereafter uses the server:start and server:stop macros to start/stop servers. This is instead of the start-jboss and stop-jboss macros that EJB3 is pulling in from testsuite/imports/server-config.xml. Should we look at doing the same in EJB3? Having 2 ways of starting/stopping the AS seems unnecessary and a possible source of problems. Also, using the server:start/stop approach helps decouple EJB3 from the testuite module. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999188#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...