activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4694) add support for flock-based shared lock file (patch included)
Date Tue, 27 Aug 2013 20:05:51 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751655#comment-13751655
] 

Timothy Bish commented on AMQ-4694:
-----------------------------------

>From reading of the legal FAQ it sounds as though it would be ok to include the JNA bits
so long as the NOTICES.txt file is amended to specify that the ASL license is being used for
that dependency.  We definitely can't include the earlier version although the build can depend
on it so we could still provide the option as long as instructions were given to the user
on how to get the library and add it into the distribution for use.  
                
> add support for flock-based shared lock file (patch included)
> -------------------------------------------------------------
>
>                 Key: AMQ-4694
>                 URL: https://issues.apache.org/jira/browse/AMQ-4694
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.8.0
>            Reporter: Carl Harris
>         Attachments: patch.txt, README.patch.txt
>
>
> This issue provides a patch to add support for using native flock (2) based lock files.
 As discussed in AMQ-4378, using the Shared File System Master/Slave configuration on an OCFS2
filesystem is complicated by Java's use of POSIX locks.  See the attached README for motivation
and description of the approach.
> With this patch, a user can configure KahaDB to use a shared native lock file (using
flock) as follows:
> {code:xml}
> <persistenceAdapter>
>   <kahaDB ...>
>     <locker>
>        <shared-native-file-locker/>
>     </locker>
>   </kahaDB>
> </persistenceAdapter>
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message