Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1851
@michaelandrepearce Agree about aggressive optimisations but not on
volatile operation's: isn't the volatile read that cost but the volatile store
that include an hidden cost a of a full barrier on x86 , to be paid on hot
paths and even if in contended. Dropoing it using lazySet or a plain store (for
size) from the functional point of view it really can't introduce any new bugs,
but is clear that is an implementation error from who has written the original
class.
---
