12:35 p.m.
Access to HAPartiiton membership is not thread-safe
---------------------------------------------------
Key: JBAS-5631
URL: http://jira.jboss.com/jira/browse/JBAS-5631
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA,
JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-4.2.0.CR2, JBossAS-5.0.0.Beta2,
JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA, JBossAS-4.0.5.CR1,
JBossAS-4.0.4.GA, JBossAS-4.0.4.CR2, JBossAS-3.2.8.SP1, JBossAS-3.2.8 Final,
JBossAS-4.0.4RC1, JBossAS-3.2.8RC1, JBossAS-4.0.3 SP1, JBossAS-4.0.3 Final,
JBossAS-4.0.3RC2, JBossAS-4.0.3RC1, JBossAS-4.0.2 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1
SP1, JBossAS-4.0.1 Final, JBossAS-4.0.1RC1, JBossAS-4.0.0 Final
Reporter: Paul Ferraro
Assigned To: Brian Stansberry
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.
--
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
4:58 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5631) Access to HAPartiiton membership is not thread-safe
[
https://jira.jboss.org/jira/browse/JBAS-5631?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-5631:
-----------------------------------
Fix Version/s: JBossAS-5.1.0.Beta1
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.1.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.
--
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
6:19 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5631) Access to HAPartiiton membership is not thread-safe
[
https://jira.jboss.org/jira/browse/JBAS-5631?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-5631:
-----------------------------------
Fix Version/s: JBossAS-5.2.0.Beta1
(was: JBossAS-5.1.0.Beta1)
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.
--
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
6:04 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5631) Access to HAPartiiton membership is not thread-safe
[
https://jira.jboss.org/jira/browse/JBAS-5631?page=com.atlassian.jira.plug...
]
Jason T. Greene updated JBAS-5631:
----------------------------------
Fix Version/s: JBossAS-6.0.0.Alpha1
(was: JBossAS-5.2.0.Beta1)
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-6.0.0.Alpha1
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.
--
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
3:35 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5631) Access to HAPartiiton membership is not thread-safe
[
https://jira.jboss.org/jira/browse/JBAS-5631?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-5631:
-----------------------------------
Fix Version/s: JBossAS-6.0.0.CR1
(was: JBossAS-6.0.0.M3)
Assignee: Paul Ferraro (was: Brian Stansberry)
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: Paul Ferraro
Fix For: JBossAS-6.0.0.CR1
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.
--
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
4:41 p.m.
New subject: [JBoss JIRA] Assigned: (JBAS-5631) Access to HAPartiiton membership is not thread-safe
[
https://jira.jboss.org/browse/JBAS-5631?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry reassigned JBAS-5631:
--------------------------------------
Assignee: Brian Stansberry (was: Paul Ferraro)
Access to HAPartiiton membership is not thread-safe
---------------------------------------------------
Key: JBAS-5631
URL: https://jira.jboss.org/browse/JBAS-5631
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: HA-Server-Core
Reporter: Paul Ferraro
Assignee: Brian Stansberry
Fix For: HA-Server-Core 1.0.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:41 p.m.
New subject: [JBoss JIRA] Moved: (JBCLUSTER-280) Access to HAPartiiton membership is not thread-safe
[
https://jira.jboss.org/browse/JBCLUSTER-280?page=com.atlassian.jira.plugi...
]
Brian Stansberry moved JBAS-5631 to JBCLUSTER-280:
--------------------------------------------------
Project: JBoss Clustering (was: JBoss Application Server)
Key: JBCLUSTER-280 (was: JBAS-5631)
Affects Version/s: (was: JBossAS-4.2.2.GA)
(was: JBossAS-5.0.0.Beta4)
(was: JBossAS-4.2.1.GA)
(was: JBossAS-5.0.0.Beta3)
(was: JBossAS-4.2.0.GA)
(was: JBossAS-5.0.0.Beta2)
(was: JBossAS-4.2.0.CR2)
(was: JBossAS-4.2.0.CR1)
(was: JBossAS-5.0.0.Beta1)
(was: JBossAS-4.0.5.GA)
(was: JBossAS-4.0.4.GA)
(was: JBossAS-4.0.5.CR1)
(was: JBossAS-4.0.4.CR2)
(was: JBossAS-3.2.8.SP1)
(was: JBossAS-3.2.8 Final)
(was: JBossAS-4.0.4RC1)
(was: JBossAS-4.0.3 Final)
(was: JBossAS-3.2.8RC1)
(was: JBossAS-4.0.3 SP1)
(was: JBossAS-4.0.3RC1)
(was: JBossAS-4.0.3RC2)
(was: JBossAS-4.0.2 Final)
(was: JBossAS-4.0.2RC1)
(was: JBossAS-4.0.1 SP1)
(was: JBossAS-4.0.1 Final)
(was: JBossAS-4.0.1RC1)
(was: JBossAS-4.0.0 Final)
Component/s: HA-Server-Core
(was: Clustering)
Fix Version/s: HA-Server-Core 1.0.0.Beta1
(was: 6.0.0.M4)
Access to HAPartiiton membership is not thread-safe
---------------------------------------------------
Key: JBCLUSTER-280
URL: https://jira.jboss.org/browse/JBCLUSTER-280
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: HA-Server-Core
Reporter: Paul Ferraro
Assignee: Brian Stansberry
Fix For: HA-Server-Core 1.0.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:42 p.m.
New subject: [JBoss JIRA] Resolved: (JBCLUSTER-280) Access to HAPartiiton membership is not thread-safe
[
https://jira.jboss.org/browse/JBCLUSTER-280?page=com.atlassian.jira.plugi...
]
Brian Stansberry resolved JBCLUSTER-280.
----------------------------------------
Resolution: Done
Fixed as part of initial work on CoreGroupMembershipService
Access to HAPartiiton membership is not thread-safe
---------------------------------------------------
Key: JBCLUSTER-280
URL: https://jira.jboss.org/browse/JBCLUSTER-280
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: HA-Server-Core
Reporter: Paul Ferraro
Assignee: Brian Stansberry
Fix For: HA-Server-Core 1.0.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5274
days inactive
5993
days old
7 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
Jason T. Greene (JIRA)
-
Paul Ferraro (JIRA)