Each server in the cluster deploys independently. If you start a server, once the app is deployed on that server and the server start is completed, the app is available on one node. As more servers finish their startup process, they (and the app) become available.
I think redeploy is a more significant issue. If at the same time you copy a new version of the app to the deploy dir of all the servers, it will be undeployed and redeployed on all the servers, and until redeploy is complete it won't be available. So, staggering the redeploys is an option to prevent this. Suggest you experiment; that's the best way to learn what will happen. If deploying your app takes too long to experiment with, write a simple webapp that has a ServletContextListener that goes to sleep for 15-30 secs in the contextInitialized() callback. Then play around with different ways of deploying it on the cluster and observe what happens. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934441#3934441 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3934441 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
