Return-Path: 
 <dev-return-40013-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A51FC101FF
	for <apmail-activemq-dev-archive@www.apache.org>;
 Tue, 27 Aug 2013 14:27:55 +0000 (UTC)
Received: (qmail 43358 invoked by uid 500); 27 Aug 2013 14:27:53 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 43178 invoked by uid 500); 27 Aug 2013 14:27:53 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 42983 invoked by uid 99); 27 Aug 2013 14:27:53 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Aug 2013 14:27:53 +0000
Date: Tue, 27 Aug 2013 14:27:53 +0000 (UTC)
From: "Carl Harris (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12665716.1377613301695.39587.1377613673052@arcas>
In-Reply-To: <JIRA.12665716.1377613301695@arcas>
References: <JIRA.12665716.1377613301695@arcas>
Subject: [jira] [Updated] (AMQ-4694) add support for flock-based shared lock
 file (patch included)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Carl Harris updated AMQ-4694:
-----------------------------

    Description: 
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}
<persistenceAdapter>
  <kahaDB ...>
    <locker>
       <shared-native-file-locker/>
    </locker>
  </kahaDB>
</persistenceAdapter>
{code}

  was:
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:

<persistenceAdapter>
  <kahaDB ...>
    <locker>
       <shared-native-file-locker/>
    </locker>
  </kahaDB>
</persistenceAdapter>


    
> 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}
> <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