"bstansberry(a)jboss.com" wrote : | They do show this test server2 was started about 50 times before this failure occurred. So, it seems quite intermittent and likely hard to track down. A key thing is understanding what exactly changed that triggered this, or if we don't really know, understanding we don't really know so we can avoid chasing the wrong thing. So, This is because each test on the clustered-testsuite will start/stop all the servers. So I believe we could make a test that only start/stops the servers until this issue appears. We could actually do that by putting a single to run in a loop. under /tests/bin you will find a way of doing this. If you contact me offline i will tell you how to use that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187579#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...