Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 54C53200CB3 for ; Mon, 26 Jun 2017 13:15:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5381C160BF8; Mon, 26 Jun 2017 11:15:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 97514160BD9 for ; Mon, 26 Jun 2017 13:15:03 +0200 (CEST) Received: (qmail 8112 invoked by uid 500); 26 Jun 2017 11:15:02 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 8101 invoked by uid 99); 26 Jun 2017 11:15:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jun 2017 11:15:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 71C44C05FC for ; Mon, 26 Jun 2017 11:15:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.011 X-Spam-Level: X-Spam-Status: No, score=-100.011 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id CU3a2wdZ-SM5 for ; Mon, 26 Jun 2017 11:15:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 395B35FDAD for ; Mon, 26 Jun 2017 11:15:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 76AA2E07DD for ; Mon, 26 Jun 2017 11:15:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 27729240C5 for ; Mon, 26 Jun 2017 11:15:00 +0000 (UTC) Date: Mon, 26 Jun 2017 11:15:00 +0000 (UTC) From: "Andrea Tarocchi (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KARAF-5222) Meke possible to force the start of a karaf instance even if another one has been detected as running. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 26 Jun 2017 11:15:04 -0000 Andrea Tarocchi created KARAF-5222: -------------------------------------- Summary: Meke possible to force the start of a karaf instance even if another one has been detected as running. Key: KARAF-5222 URL: https://issues.apache.org/jira/browse/KARAF-5222 Project: Karaf Issue Type: Improvement Components: karaf-core, karaf-instance Affects Versions: 4.1.1 Reporter: Andrea Tarocchi For debug or troubleshooting purposes would be good to have a way to force the run, through bin/kara script, of a karaf instance even if another one (the root one) has been detected as already running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)