activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3301) LockFile in-jvm check is not thread-safe
Date Sun, 15 Apr 2012 04:53:28 GMT

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

Rob Davies resolved AMQ-3301.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.6.0
         Assignee: Rob Davies

Patch applied in SVN revision 1326252
                
> LockFile in-jvm check is not thread-safe
> ----------------------------------------
>
>                 Key: AMQ-3301
>                 URL: https://issues.apache.org/jira/browse/AMQ-3301
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>            Reporter: Arthur Naseef
>            Assignee: Rob Davies
>            Priority: Minor
>             Fix For: 5.6.0
>
>         Attachments: amq-3301.patch
>
>
> kahadb/src/main/java/org/apache/kahadb/util/LockFile.java adds in-JVM locking to Channel.tryLock()
using system properties.  However, there is time between the read-and-check for an existing
lock and setting a new lock.
> I found this problem while running multiple brokers in a single JVM for diagnostic purposes
with two brokers using a shared directory to simlute a production H/A environment.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message