Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BE067CF3C for ; Mon, 26 Jan 2015 13:30:37 +0000 (UTC) Received: (qmail 37206 invoked by uid 500); 26 Jan 2015 13:30:34 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 37095 invoked by uid 500); 26 Jan 2015 13:30:34 -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 37084 invoked by uid 99); 26 Jan 2015 13:30:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2015 13:30:34 +0000 Date: Mon, 26 Jan 2015 13:30:34 +0000 (UTC) From: "Rod Widdowson (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DAEMON-329) Can procrun detect the JVM without consulting the registry MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Rod Widdowson created DAEMON-329: ------------------------------------ Summary: Can procrun detect the JVM without consulting the registry Key: DAEMON-329 URL: https://issues.apache.org/jira/browse/DAEMON-329 Project: Commons Daemon Issue Type: Improvement Components: Procrun Affects Versions: 1.0.15 Environment: Windows Server2012 R2 Java server installed from the tarball Reporter: Rod Widdowson Priority: Minor For reasons I do not fully comprehend, Oracle distribute the Windows Server JVM as a tarball. This means that none of the "usual" registry setting are written. Our (the Shibboleth protect's) latest IdP release ships with an MSI which bundles Procrun to launch the J2EE container. We set up the HKLM\Software\Wow6432Node\Apache Software Key\Procrun 2.0\ appropriately, specifically setting 'Parameters\Java\JavaHome' appropriately and 'Parameters\Java\jvm' to 'auto'. I can provide full details available if you want. We recently had a customer raise an issue that the autodetect of the jvm.dll wasn't working. AFAICS this customer installed from the tarball. This is easily fixed by setting 'jvm' appropriately, and I am modifying our documentation to explain what to do.. This RFE is to see if there is anyway that this can be automated inside procun. It knows the home directory and so it should be able to locate the jvm.dll. Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)