[jboss-dev-forums] [Design of Clustering on JBoss (Clusters/JBoss)] - Testsuite changes

bstansberry@jboss.com do-not-reply at jboss.com
Wed Aug 9 22:47:45 EDT 2006


Just an FYI on some stuff I'm doing that affects the way the clustering tests work.

The following is currently in place in Branch_4_0 and will be moved to HEAD soon.

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.

This is a real problem right now, as cc is starting to use jrockit, and odd failures are appearing.  I don't run jrockit at home, so hard to diagnose w/o logs.

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


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964222#3964222

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964222



More information about the jboss-dev-forums mailing list