-------------------------------------------------------------------------------------------------------- - Have one tomcat/JBoss instance. - Deploy multiple webapps to it, using the release number as part of the webapp name, e.g. myapp-1.0, myapp-1.1, myapp-1.2. - Have the testers use the tomcat manager webapp to stop those webapps they're not testing. You can also completely undeploy webapps you don't need to test anymore so they don't consume any resources.
Finally, as another alternative, maybe you can do most of your testing with a result data set. That way the app won't require as much memory. Have one "big" test server setup with 512MB or however much you need, and many smaller ones with say 64MB. --------------------------------------------------------------------------------------------------------
hmmmm... this is the last way I might try.. because it is tough to modify only a war file name and leave it working, I have to configure many source code ... :~( nono it must make me crazy finally..
my current status is to use multiple tomcat instance, one jboss instance and one mysql instance. it is already challengable enough because only some versions of jboss support multiple servers binding..
"result data set" -- what's that ? sounds interesting :)
with best wishes
Zheng Sun
_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
