Return-Path: 
 <derby-user-return-15498-apmail-db-derby-user-archive=db.apache.org@db.apache.org>
X-Original-To: apmail-db-derby-user-archive@www.apache.org
Delivered-To: apmail-db-derby-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 28F07108CB
	for <apmail-db-derby-user-archive@www.apache.org>;
 Thu, 27 Feb 2014 10:49:05 +0000 (UTC)
Received: (qmail 295 invoked by uid 500); 27 Feb 2014 10:49:04 -0000
Delivered-To: apmail-db-derby-user-archive@db.apache.org
Received: (qmail 99875 invoked by uid 500); 27 Feb 2014 10:48:56 -0000
Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-user-help@db.apache.org>
list-unsubscribe: <mailto:derby-user-unsubscribe@db.apache.org>
List-Post: <mailto:derby-user@db.apache.org>
List-Id: <derby-user.db.apache.org>
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Delivered-To: mailing list derby-user@db.apache.org
Received: (qmail 99862 invoked by uid 99); 27 Feb 2014 10:48:55 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Feb 2014 10:48:55 +0000
X-ASF-Spam-Status: No, hits=-2.3 required=5.0
	tests=RCVD_IN_DNSWL_MED,SPF_PASS,UNPARSEABLE_RELAY
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of Dyre.Tjeldvoll@oracle.com
 designates 156.151.31.81 as permitted sender)
Received: from [156.151.31.81] (HELO userp1040.oracle.com) (156.151.31.81)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Feb 2014 10:48:47 +0000
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94])
	by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id
 s1RAmOKb003609
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <derby-user@db.apache.org>; Thu, 27 Feb 2014 10:48:25 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230])
	by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s1RAmNJ0014111
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <derby-user@db.apache.org>; Thu, 27 Feb 2014 10:48:24 GMT
Received: from abhmp0015.oracle.com (abhmp0015.oracle.com [141.146.116.21])
	by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s1RAmNi0009426
	for <derby-user@db.apache.org>; Thu, 27 Feb 2014 10:48:23 GMT
Received: from atum20.no.oracle.com (/10.172.139.200)
	by default (Oracle Beehive Gateway v4.0)
	with ESMTP ; Thu, 27 Feb 2014 02:48:23 -0800
Message-ID: <530F17E8.6060401@oracle.com>
Date: Thu, 27 Feb 2014 11:48:08 +0100
From: Dyre Tjeldvoll <Dyre.Tjeldvoll@oracle.com>
Organization: Oracle
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: derby-user@db.apache.org
Subject: Re: Apache Derby Command Line?
References: <53053A1E.4000206@videotron.ca> <5307FCD2.2000301@gmail.com>
 <1393033697453-137339.post@n7.nabble.com>
 <EF3DF51E-83D1-4C53-9A25-C69168574D3E@yahoo.com>
 <1393093344047-137342.post@n7.nabble.com>
In-Reply-To: <1393093344047-137342.post@n7.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
X-Virus-Checked: Checked by ClamAV on apache.org

On 02/22/2014 07:22 PM, Turtles wrote:
> I have java working properly (so ignore the quotes and anything else that
> looks wrong).  That isint the issue, its getting derby to load properly.
> FireDaemon loads the process a little differently than the command line but
> it works because other java applications ive run as services run fine
> (tomcat for example).

I'm not familiar with FireDaemon, so the following may not be relevant.

I was faced with a similar issue when trying to create Windows services 
for a server that had to be started with a long and complicated command 
line. I was able to start the server in cmd.exe just fine, but when 
issuing the net start <service> command it would fail with strange errors.

After some googling I discovered that there are registry entries that 
contain the string used to start the service. By inspecting that reg. 
entry after creating my service, I could see that the command line was 
being mangled in various ways if it contained spaces or other special 
characters. Some things I managed to work around by adding various 
quotes and escapes, but not always.

One thing to check is whether your daemon/service facility uses a 
command interpreter (e.g. cmd.exe) when starting the executable. If so, 
you may have to quote things that should not be expanded twice, once for 
the command line creating the service, and once for the starting of the 
service.

White space in command line arguments are particularly troublesome as 
you must prevent spaces from being interpreted as argument separators 
both when creating and launching the service.

HTH,

Dyre