Return-Path: Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: (qmail 97524 invoked from network); 20 Oct 2010 22:16:48 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Oct 2010 22:16:48 -0000 Received: (qmail 18899 invoked by uid 500); 20 Oct 2010 22:16:48 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 18842 invoked by uid 500); 20 Oct 2010 22:16:48 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 18834 invoked by uid 99); 20 Oct 2010 22:16:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Oct 2010 22:16:48 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Oct 2010 22:16:46 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9KMGODh004798 for ; Wed, 20 Oct 2010 22:16:25 GMT Message-ID: <14010796.20681287612984971.JavaMail.jira@thor> Date: Wed, 20 Oct 2010 18:16:24 -0400 (EDT) From: "Sebb (JIRA)" To: issues@commons.apache.org Subject: [jira] Resolved: (DAEMON-182) Procrun documentation incorrectly states that the StartPath is *not* used when in jvm StartMode In-Reply-To: <9807942.20031287610585046.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DAEMON-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved DAEMON-182. ------------------------- Resolution: Fixed Fix Version/s: 1.0.4 Thanks, fixed. > Procrun documentation incorrectly states that the StartPath is *not* used when in jvm StartMode > ----------------------------------------------------------------------------------------------- > > Key: DAEMON-182 > URL: https://issues.apache.org/jira/browse/DAEMON-182 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun > Affects Versions: 1.0.3 > Reporter: Steve Ash > Priority: Trivial > Fix For: 1.0.4 > > > This is just a problem with the documentation on the website on the procrun page. The description for the StartPath option states that this option is not applicable for jvm StartMode. This is incorrect. In serviceStart in prunsrv.c the Win32 call SetCurrentDirectory is made with the StartPath option before starting up the JVM. Thus, the working directory for the process is set before the jvm (and the classloaders) try to resolve any file names. > This is important, because without StartPath set, then the working directory defaults to the Windows directory (e.g. C:\Windows). Thus, if any relative paths are used anywhere (classpath, etc.) then nothing will resolve. In my case the service control manager received a 3 return code from procrun indicating that the main class could not be found (which is true-- my classpath was all built with relative paths). Setting the StartPath property corrected my problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.