Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Thu, 7 Jan 2016 18:52:39 +0000 (UTC)
From: "Christian Schneider (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12917636.1449074320000.46858.1452192759928@Atlassian.JIRA>
In-Reply-To: <JIRA.12917636.1449074320000@Atlassian.JIRA>
References: <JIRA.12917636.1449074320000@Atlassian.JIRA>
 <JIRA.12917636.1449074320027@arcas>
Subject: [jira] [Commented] (KARAF-4166) Add karaf.lock.exclusive property
 to prevent a slave instance to start
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-4166?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1508=
7865#comment-15087865 ]=20

Christian Schneider commented on KARAF-4166:
--------------------------------------------

A lock is always exclusive. I think the naming might be misleading.

> Add karaf.lock.exclusive property to prevent a slave instance to start
> ----------------------------------------------------------------------
>
>                 Key: KARAF-4166
>                 URL: https://issues.apache.org/jira/browse/KARAF-4166
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-core
>            Reporter: Jean-Baptiste Onofr=C3=A9
>            Assignee: Jean-Baptiste Onofr=C3=A9
>             Fix For: 3.0.6, 4.0.4
>
>
> By default, a Karaf slave instance starts to be able to "pre-install" bun=
dle there.
> We can enhance the SimpleLockFile (controled a karaf.lock.exclusive prope=
rty) like this:
> {code}
> boolean lock() throws Exception {
>  boolean locked =3D super.lock();
>  if (!locked) throw new RuntimeException("startup aborted");
>  return true;
> }
> {code}


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