Hi all,
I just committed a cluster upgrade test to the admin dev tests. It's commented out of the cli target because it can't pass without some issues being fixed. But it can be run with the param: -Dteststorun=cluster-upgrade
Question 1:
The instances do not come up all the way due to several startup errors. The output is:
upin1: Timed out waiting for upin1 to start.
upin2: Timed out waiting for upin2 to start.
The command start-instance failed for: upin1 upin2
...and yet the test passes (the asadmin command returns true). Is that expected?
Question 2:
Because of the timeouts, the instances are semi-running (there is a Java process and they're sending GMS announcements that they're up), but can't be stopped with stop-cluster. So after the test exits there are still 4 Java processes running for the the two instances. Is there something else I can do in the test to clean this up?
If someone is looking for a way to test the robustness of start/stop cluster, here's a good test case for you (until everything is working normally again)
Admin test info again:
http://wikis.sun.com/display/GlassFish/AdminTests
See the comments in ClusterUpgradeTest.java for full details.
Thanks,
Bobby