commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rod Widdowson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DAEMON-329) Can procrun detect the JVM without consulting the registry
Date Mon, 26 Jan 2015 13:30:34 GMT
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)

Mime
View raw message