You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2015/08/04 14:52:04 UTC

[jira] [Updated] (AMQ-5787) VMTransport uses broken double checked locking

     [ https://issues.apache.org/jira/browse/AMQ-5787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp updated AMQ-5787:
-----------------------------
    Fix Version/s: 5.11.2

> VMTransport uses broken double checked locking
> ----------------------------------------------
>
>                 Key: AMQ-5787
>                 URL: https://issues.apache.org/jira/browse/AMQ-5787
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Transport
>    Affects Versions: 5.11.1
>            Reporter: james
>            Assignee: Timothy Bish
>            Priority: Critical
>             Fix For: 5.11.2, 5.12.0
>
>
> the VMTransport.getMessageQueue() method uses the "double checked locking" idiom to avoid the synchronization overhead if the messageQueue has already been instantiated.  however, this idiom is broken unless the reference is marked as volatile.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)