[Jboss-dev-forums] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: org.jboss.ha.framework.server.FarmMemberService behaviou

[garu <nu...@jb...>]

Well, that piece of code contributes to expose a problem that exists during the service startup.

I have been successful in reproducing the following scenario.

1- server starts up and joins the cluster, /farm applications are pulled from remote node.
2- farmDeploy() is called for the applications, remotelyDeployed gets filled with their names
3- scanner thread is started and begins calling deploy() for each application
4- by chance, deploy() executes while service status is still STARTING so it call super.deploy() and applications are deployed but their names are not removed from remotelyDeployed
5- you remove application from /farm and farmUndeploy() is invoked.
6- you put again application in /farm, deploy() is called, super.deploy() is called, BUT remotelyDeployed is still dirty from the preceding deploy so farmDeploy() is not invoked and the application won't get farmed

Then everything cleans up and for subsequent deploy/undeploy works correctly.

Gabriele.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877983#3877983

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877983