[jboss-jira] [JBoss JIRA] Updated: (JBAS-5631) Access to HAPartiiton membership is not thread-safe

Access to HAPartiiton membership is not thread-safe --------------------------------------------------- Key: JBAS-5631 URL: https://jira.jboss.org/jira/browse/JBAS-5631 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Components: Clustering Affects Versions: JBossAS-4.0.0 Final, JBossAS-4.0.1RC1, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.2RC1, JBossAS-4.0.2 Final, JBossAS-4.0.3RC1, JBossAS-4.0.3RC2, JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1, JBossAS-3.2.8RC1, JBossAS-4.0.4RC1, JBossAS-3.2.8 Final, JBossAS-3.2.8.SP1, JBossAS-4.0.4.CR2, JBossAS-4.0.4.GA, JBossAS-4.0.5.CR1, JBossAS-4.0.5.GA, JBossAS-5.0.0.Beta1, JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR2, JBossAS-4.2.0.GA, JBossAS-4.2.1.GA, JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta3, JBossAS-5.0.0.Beta4 Reporter: Paul Ferraro Assignee: Brian Stansberry Fix For: JBossAS-5.2.0.Beta1 There are 2 problems with the current implementation. 1. Currently, the membership collections, while synchronized, are both non-volatile and updated in a non-final fashion, so concurrent access by both view changes and rpc invocations is not thread-safe. 2. Membership is expressed in 4 different vectors. During view change, these vectors are not updated atomically. To address both problems, the 4 vectors ought to be encapsulated into a single volatile, immutable object.