8020860: cluster Hashtable/Vector field updates for better transactional memory behaviour

Martin Buchholz martinrb at google.com
Tue Mar 25 20:59:24 UTC 2014

On Tue, Mar 25, 2014 at 1:37 PM, Mike Duigou <mike.duigou at oracle.com> wrote:

> There is a slight behaviour change introduced in this changeset.
> Previously some methods updated the modcount unconditionally updated even
> when an ArrayIndexOutOfBoundsException was subsequently thrown for an
> invalid index and the Vector was not modified. With this change the
> modcount will only be updated if the Vector is actually changed. It is not
> expected that applications will have relied or should have relied on this
> behaviour.
I don't think the modCount behavior should be changed.  Although no one
should be relying on the current behavior and few people are, any change in
behavior needs a good reason, and I don't see a good enough one here - it's
not clear which behavior is actually better.

More information about the core-libs-dev mailing list