anonymous wrote : 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? |
Sure, this would work. Others have followed this approach as well to work around the farm deployment issues. The central farm url (perhaps a shared filesystem) can be a single point of failure but you could add a secondary (alternative) farm folder in case the shared filesystem crashes. Regarding your other question of what the timetable is for fixing this. The problem has been recorded in the Jira system and design forums, however, there is no timetable set for resolving these issues. http://jira.jboss.com/jira/browse/JBAS-1322 describes the problem that you have hit. http://jira.jboss.com/jira/browse/JBAS-2326 describes a problem that you could hit if connectivity between nodes breaks and latest resumes (cluster nodes continue to run throughout this situation but do not react to changes made while disconnected from the rest of cluster.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956283#3956283 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956283 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
