-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 6
-
Component/s: core-libs
-
b53
-
generic
-
generic
Paragraphs such as the following should make it clearer how the
concurrent classes fit into the Java Memory Model.
* <p>
* Memory visibility effects: As with other concurrent collections, state
* changes to any object made prior to placing it into a <tt>CopyOnWriteArrayList</tt>
* <a href="package-summary.html#MemoryVisibility"><i>happen-before</i></a>
* that element is accessed via or removed from the <tt>CopyOnWriteArrayList</tt>.
concurrent classes fit into the Java Memory Model.
* <p>
* Memory visibility effects: As with other concurrent collections, state
* changes to any object made prior to placing it into a <tt>CopyOnWriteArrayList</tt>
* <a href="package-summary.html#MemoryVisibility"><i>happen-before</i></a>
* that element is accessed via or removed from the <tt>CopyOnWriteArrayList</tt>.