[
https://issues.apache.org/jira/browse/AMQ-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262019#comment-15262019
]
ASF subversion and git services commented on AMQ-6251:
------------------------------------------------------
Commit bb58db75a677e3cc147f3ca0a56ffb9afa12d287 in activemq's branch
refs/heads/activemq-5.13.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=bb58db7 ]
https://issues.apache.org/jira/browse/AMQ-6251
Make field volatile since it is written to outside of any locks and read
both in and out of locking.
(cherry picked from commit 8031d77f984e4d3c54782dd4934f48b35cf16c00)
> Queue resetNeeded field should be volatile
> ------------------------------------------
>
> Key: AMQ-6251
> URL: https://issues.apache.org/jira/browse/AMQ-6251
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.1, 5.13.2
> Reporter: james
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.14.0
>
>
> The Queue.resetNeeded field should be volatile due to the fact that it is
> exposed outside of any additional synchronization (via the
> Queue.isResetNeeded() method). without the volatile modifier, the flag could
> be set but not recognized by any external code checking it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
