[jboss-jira] [JBoss JIRA] Updated: (JGRP-459) disable_initial_coord not working

[Bela Ban (JIRA)]

     [ http://jira.jboss.com/jira/browse/JGRP-459?page=all ]

Bela Ban updated JGRP-459:
--------------------------

    Fix Version/s: 2.5
         Priority: Minor  (was: Major)

> disable_initial_coord not working 
> ----------------------------------
>
>                 Key: JGRP-459
>                 URL: http://jira.jboss.com/jira/browse/JGRP-459
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4.1 SP1
>         Environment: mac os x, Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
>            Reporter: Graeme Ahokas
>         Assigned To: Bela Ban
>            Priority: Minor
>             Fix For: 2.5
>
>
> We've got the following scenario: three applications, App1, App2, and App3. We want App3 to be the coordinator when the apps first start, so there is no confusion about multiple groups / coordinators. So, we set App1 and App2's disable_initial_coord = true, and App3's disable_initial_coord=false. 
> Then we start App1, and it will wait. Then we start App2, and App1 / App2 will determine a coordinator, even though disable_initial_coord is set to true for both, and we have not started App3 yet! This seems to conflict with the documentation which states: 
> Note that - if a member is started as first member of a group - but its property is set to true, then it will loop until another member whose disable_initial_coord property is set to false, is started. 
> We need disable_initial_coord to work as documented.

-- 
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