[jboss-jira] [JBoss JIRA] Updated: (JBAS-2292) DistributedReplicantManager does not honor jmx service dependencies when notifiyng a node removal

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated JBAS-2292:
-----------------------------------

    Fix Version/s: Backlog
                       (was: No Release)


> DistributedReplicantManager does not honor jmx service dependencies when notifiyng a node removal
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-2292
>                 URL: https://jira.jboss.org/jira/browse/JBAS-2292
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.0.2 Final
>         Environment: Jboss 4.0.2, 
> WinXP
> JDK 1.5
>            Reporter: janssk1
>            Assignee: Brian Stansberry
>             Fix For: Backlog
>
>
> We are using some HASingletonServices. These services use the HAJNDI tree to lookup other services. 
> Both the HASingletonservices and the HAJNDI service are notified if a node (eg the master) is removed from the cluster. However, the order seems to be random. If the master goes down, the HASingletonservce seems to be notified first. It tries to start the singleton on another host. While starting, it uses the HAJNDI, but this one still tries to connect to the old server, leading to NamingExceptions. 
> Since i added a jmx depencency from the singleton service to HAJNDI, i would expect that the HAJNDI gets notified first. That would fix my problem. 
> I looked in the code of the DistributedReplicantManagerImpl and it seems that this one does not keep track of the order in which keys are registered. I quickly changed all HashMap and HashSet instantiations of this class to LinkedHashMap and LinkedHashSet instantiations, and now my problem is fixed. 

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