Hi, thanks for the information. I'm running into this issue as well. I have a cluster of several nodes and just want to be able to have nodes go down and come up at random and not have clients notice (assumption is that at least one node will be up at any given time)... as it is, in a simple two node cluster I've been testing on, if one node goes down and then comes back up, unless I manually trigger hot deployment somehow, coming back up will use cold deployment and that node will be useless since my app won't be loaded.
So I have two questions: Is there a recommended best practice for deployment that can mitigate this issue? For example, would having each node point to a central HTTP farm URL help at all, since it might be easier to trigger hot deployment everywhere by updating the "last modified" time on the centrally-distributed file? And is there any projected timetable for a fix of the underlying issue itself? Thanks, --Erik View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956253#3956253 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956253 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
