Maintain the server logs for the different testsuite clustering configs ----------------------------------------------------------------------- Key: JBAS-3506 URL: http://jira.jboss.com/jira/browse/JBAS-3506 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Test Suite Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta Previously the clustering tests worked by creating 2 configs "node0" and "node1" and launching 2 jboss instances, one using each. To execute all the required tests, the build script would tear down and rebuild node0 and node1, altering various aspects of the config (e.g. use REPL_SYNC instead of REPL_ASYNC). The problem with this is that when a version of node0/1 got torn down and replaced, it's server logs went with it. This makes subsequent debugging of any failures difficult, particularly with cruisecontrol runs that sometimes reveal problems we don't see on our local machines. To fix this, I'm no longer using "node0/node1". Rather, each config will be given a name that somewhat describes what it is, e.g.: cluster-UDP-0 and cluster-UDP-1 cluster-field-UDP-0/1 (configured for FIELD repl) cluster-UDP-SYNC-0/1 (configured for REPL_SYNC) cluster-field-UDP-SYNC-0/1 cluster-UDP-BR-0/1 (configured for BuddyReplication) cluster-field-UDP-BR-0/1 Equivalent configs will be created for the tests running the TCP stack. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira