Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 25 Sep 2012 21:52:08 +1100 (NCT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <721537220.121426.1348570328453.JavaMail.jiratomcat@arcas>
In-Reply-To: <1898551887.121329.1348568287721.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (AMQ-4075) More transparent KahaDB file lock
 switch
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/AMQ-4075?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D134626=
38#comment-13462638 ]=20

Claus Ibsen commented on AMQ-4075:
----------------------------------

Yeah I wonder if we can introduce an attribute in the xml namespace, so you=
 can configure it on the kahaDB adapter
               =20
> More transparent KahaDB file lock switch
> ----------------------------------------
>
>                 Key: AMQ-4075
>                 URL: https://issues.apache.org/jira/browse/AMQ-4075
>             Project: ActiveMQ
>          Issue Type: Wish
>          Components: Message Store
>    Affects Versions: 5.6.0
>            Reporter: Petr N=C3=ADdl
>            Priority: Minor
>             Fix For: 5.8.0
>
>
> Would it be possible to change the way in which KahaDB file locking can b=
e disabled? Currently this can be accomplished by setting 'java.nio.channel=
s.FileLock.broken' system property. But system property settings can influe=
nce other parts of the system where this behavior is not desirable. This es=
pecially apply for enterprise systems where ActiveMQ is embedded in the app=
lication and therefore shares the same JVM.

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