From: garu <nu...@jb...> - 2005-05-18 10:52:48
|
Opened Bug http://jira.jboss.com/jira/browse/JBCLUSTER-42. I tested the proposed solution and it looks to be working. As for my first question, now i see the need for that date check within the pullNewDeployments() method: stop/start the service from jmx console! Sorry i didn't thought of that. One more thing, i'm writing for my own usage a FarmMemberSingletonService that's modeled on FarmMemberService, ie it farms the applications in all the cluster nodes like it, but deployes them only in the singleton master so that if it goes down the new master is sure to have the correct apps version to deploy. Right now it works, but for the logic to control the service start/stop from jmx console that i have still to implement. I wished to extend FarmMemberService, but it is not easily extendable for such task unless some refactoring is done in URLDeploymentScanner and FarmMemberService so i had to duplicate the code adding some more logic. I'm wondering if you might be interested in including that service in Jboss once it is finished. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878173#3878173 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878173 |