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 46106200B5B for ; Fri, 5 Aug 2016 21:52:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 44C1E160A8E; Fri, 5 Aug 2016 19:52:10 +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 66D49160A64 for ; Fri, 5 Aug 2016 21:52:09 +0200 (CEST) Received: (qmail 23744 invoked by uid 500); 5 Aug 2016 19:52:08 -0000 Mailing-List: contact user-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@karaf.apache.org Delivered-To: mailing list user@karaf.apache.org Received: (qmail 23732 invoked by uid 99); 5 Aug 2016 19:52:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2016 19:52:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 223FE18624C for ; Fri, 5 Aug 2016 19:52:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.28 X-Spam-Level: ** X-Spam-Status: No, score=2.28 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ka40ezTpU0Hg for ; Fri, 5 Aug 2016 19:52:05 +0000 (UTC) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 6E35C5F4E3 for ; Fri, 5 Aug 2016 19:52:05 +0000 (UTC) Received: from mfilter29-d.gandi.net (mfilter29-d.gandi.net [217.70.178.160]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id A517617209D for ; Fri, 5 Aug 2016 21:51:59 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter29-d.gandi.net Received: from relay4-d.mail.gandi.net ([IPv6:::ffff:217.70.183.196]) by mfilter29-d.gandi.net (mfilter29-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id nLkbVMUE6FQr for ; Fri, 5 Aug 2016 21:51:58 +0200 (CEST) X-Originating-IP: 78.244.148.153 Received: from [192.168.134.3] (ser34-1-78-244-148-153.fbx.proxad.net [78.244.148.153]) (Authenticated sender: jb@nanthrax.net) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id EABC01720A3 for ; Fri, 5 Aug 2016 21:51:57 +0200 (CEST) In-Reply-To: References: X-Referenced-Uid: 1056284 Thread-Topic: service wrapper bug? User-Agent: Type for Android MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----HSLZ9WYRBRL0APVM25QNJ6JIQCV1BH" Content-Transfer-Encoding: 8bit Subject: Re: service wrapper bug? From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= Date: Fri, 05 Aug 2016 21:51:55 +0200 To: user@karaf.apache.org Message-ID: <03d210c7-c78f-4b2d-a584-2e8b7a8df850@typeapp.com> archived-at: Fri, 05 Aug 2016 19:52:10 -0000 ------HSLZ9WYRBRL0APVM25QNJ6JIQCV1BH Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Hi Scott Can you create a Jira about that ? I will take a look. Thanks Regards JB On Aug 5, 2016, 21:48, at 21:48, "Leschke, Scott" wrote: >Ran into a minor issue using the service-wrapper feature on Karaf >4.0.5/Windows. > >After installing the feature, we ran the wrapper:install command per >the docs. That worked fine. When we tried to start the service though >it failed. Upon review, I saw that the {service-name}-wrapper.conf >file had the following lines in it. This file is created under >KARAF_BASE/etc. > >wrapper.java.classpath.2=%KARAF_HOME%/lib/wrapper/*.jar >wrapper.java.library.path.1=%KARAF_HOME%/lib/wrapper/ > >I've redefined KARAF_BASE to be outside the KARAF_HOME hierarchy. >Changing these two lines to the following allowed the service to start. > >wrapper.java.classpath.2=%KARAF_BASE%/lib/wrapper/*.jar >wrapper.java.library.path.1=%KARAF_BASE%/lib/wrapper/ > > >I'm assuming this is the correct solution as wrapper:install created >the bin and lib folders under KARAF_BASE (bin and lib) and not >KARAF_HOME. >Would it also be fair to assume this is a known issue? > >Regards, > >Scott ------HSLZ9WYRBRL0APVM25QNJ6JIQCV1BH Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi Scott

Can you create a Jira about that ? I will take a look.

Thanks
Regards
JB

On Aug 5, 2016, at 21:48, "Leschke, Scott" <SLeschke@medline.com> wrote:

Ran into a minor issue using the service-wrapper feature on Karaf 4.0.5/Windows.

 

After installing the feature, we ran the wrapper:install command per the docs.  That worked fine. When we tried to start the service though it failed.  Upon review, I saw that the {service-name}-wrapper.conf file had the following lines in it.  This file is created under KARAF_BASE/etc.

 

wrapper.java.classpath.2=%KARAF_HOME%/lib/wrapper/*.jar

wrapper.java.library.path.1=%KARAF_HOME%/lib/wrapper/

 

I’ve redefined KARAF_BASE to be outside the KARAF_HOME hierarchy.  Changing these two lines to the following allowed the service to start.

 

wrapper.java.classpath.2=%KARAF_BASE%/lib/wrapper/*.jar

wrapper.java.library.path.1=%KARAF_BASE%/lib/wrapper/

 

 

I’m assuming this is the correct solution as wrapper:install created the bin and lib folders under KARAF_BASE (bin and lib) and not KARAF_HOME.

Would it also be fair to assume this is a known issue?

 

Regards,

 

Scott

------HSLZ9WYRBRL0APVM25QNJ6JIQCV1BH--