[jboss-jira] [JBoss JIRA] Reopened: (JBCLUSTER-42) First deploy after joining a cluster is not farmed

Brian Stansberry (JIRA) jira-events at lists.jboss.org
Sat Apr 12 12:21:56 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBCLUSTER-42?page=all ]

Brian Stansberry reopened JBCLUSTER-42:
---------------------------------------

             
Re-open to replace Affects Version

> First deploy after joining a cluster is not farmed
> --------------------------------------------------
>
>                 Key: JBCLUSTER-42
>                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-42
>             Project: JBoss Clustering
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: Q2Y5
>         Environment: Jboss 4.0.2 final, Java 1.5.0_02
>            Reporter: Gabriele Garuglieri
>         Assigned To: Scott Marlow
>             Fix For: Q2Y5
>
>          Time Spent: 3 hours
>  Remaining Estimate: 0 minutes
>
> There a problem in org.jboss.ha.framework.server.FarmMemberService that shows during service startup.
> It happens with 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.
> I tested the solution proposed by Scott Marlow Novell to move the clearing of "remotelyDeployed" flag before the "getState() == STARTING" test and it looks to be working.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list