[jira] [Commented] (DAEMON-329) Can procrun detect the JVM without consulting the registry
[ https://issues.apache.org/jira/browse/DAEMON-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864083#comment-16864083 ] Rod Widdowson commented on DAEMON-329: -- You knew this anyway, but this works like a dream. We'll bundle wirh procrun 1.1.1 as soon as its available. > 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 > Fix For: 1.1.1 > > > 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 (v7.6.3#76005)
[jira] [Commented] (DAEMON-329) Can procrun detect the JVM without consulting the registry
[ https://issues.apache.org/jira/browse/DAEMON-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863859#comment-16863859 ] Rod Widdowson commented on DAEMON-329: -- Awesome mark. Thanks. > 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 > Fix For: 1.1.1 > > > 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 (v7.6.3#76005)
[jira] [Commented] (DAEMON-329) Can procrun detect the JVM without consulting the registry
[ https://issues.apache.org/jira/browse/DAEMON-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863784#comment-16863784 ] Rod Widdowson commented on DAEMON-329: -- [~markt], can I ask a follow up question? Just this week [I got a report|https://issues.shibboleth.net/jira/browse/IDP-1466] that there are similar issues with JDKs. It feels like the JDK is going to be deployed by end users more and more these days, so I stopped ignoring this issue. Is there a chance that the fix for this also handles JDK distributions? And if so do you have a list somewhere of Distros that are known/assumed/tested to work? Finally, is it work catching an intermeidate build of this and testing it or should I just way for 1.1 to ship? Thanks > 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 > Fix For: 1.1.1 > > > 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 (v7.6.3#76005)
[jira] [Commented] (DAEMON-348) Clearing the "Thread Stack Size" field leaves service unstartable
[
https://issues.apache.org/jira/browse/DAEMON-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299845#comment-15299845
]
Rod Widdowson commented on DAEMON-348:
--
> So are you saying that the code should remove the JvmSs entry if the
> ThreadStackSize (TSS) field is emptied?
Absolutely. I brought my customer's machine back to life by doing just that.
> I assume it does not create the entry if the TSS field is empty on initial
> creation.
Correct. It only gets populated when you change it.
> I don't have a Windows system handy at present to check
I have _loads_ of windows VMs lieing about if you need me to run tests.
/Rod
> Clearing the "Thread Stack Size" field leaves service unstartable
> -
>
> Key: DAEMON-348
> URL: https://issues.apache.org/jira/browse/DAEMON-348
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
>Affects Versions: 1.0.15
> Environment: Windows7 x86
>Reporter: Rod Widdowson
>
> Just diagnosed an issue with a customer in which the java [process was
> unrunnable). This was because
> {{HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun
> 2.0\shibd_idp\Parameters\Java\JvmSs}} was zero, (where {{shibd_idp}} is the
> service.
> I managed to reproduce this behavior by
> * starting shibd_idpw (a.k.a prunmgr.exe)
> * modifying Thread Stack Size to be something
> * (verify with regedit)
> * clear the Thread Stack Size field
> * JvmSs is now zero
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DAEMON-348) Clearing the "Thread Stack Size" field leaves service unstartable
[
https://issues.apache.org/jira/browse/DAEMON-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rod Widdowson updated DAEMON-348:
-
Description:
Just diagnosed an issue with a customer in which the java [process was
unrunnable). This was because
{{HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun
2.0\shibd_idp\Parameters\Java\JvmSs}} was zero, (where {{shibd_idp}} is the
service.
I managed to reproduce this behavior by
* starting shibd_idpw (a.k.a prunmgr.exe)
* modifying Thread Stack Size to be something
* (verify with regedit)
* clear the Thread Stack Size field
* JvmSs is now zero
was:
Just diagnosed an issue with a customer in which the java [process was
unrunnable). This was because {{ HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software
Foundation\Procrun 2.0\shibd_idp\Parameters\Java\JvmSs}} was zero, (where
{{shibd_idp}} is the service.
I managed to reproduce this behavior by
* starting shibd_idpw (a.k.a prunmgr.exe)
* modifying Thread Stack Size to be something
* (verify with regedit)
* clear the Thread Stack Size field
* JvmSs is now zero
> Clearing the "Thread Stack Size" field leaves service unstartable
> -
>
> Key: DAEMON-348
> URL: https://issues.apache.org/jira/browse/DAEMON-348
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
>Affects Versions: 1.0.15
> Environment: Windows7 x86
>Reporter: Rod Widdowson
>
> Just diagnosed an issue with a customer in which the java [process was
> unrunnable). This was because
> {{HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun
> 2.0\shibd_idp\Parameters\Java\JvmSs}} was zero, (where {{shibd_idp}} is the
> service.
> I managed to reproduce this behavior by
> * starting shibd_idpw (a.k.a prunmgr.exe)
> * modifying Thread Stack Size to be something
> * (verify with regedit)
> * clear the Thread Stack Size field
> * JvmSs is now zero
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DAEMON-348) Clearing the "Thread Stack Size" field leaves service unstartable
[
https://issues.apache.org/jira/browse/DAEMON-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rod Widdowson updated DAEMON-348:
-
Description:
Just diagnosed an issue with a customer in which the java [process was
unrunnable). This was because {{ HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software
Foundation\Procrun 2.0\shibd_idp\Parameters\Java\JvmSs}} was zero, (where
{{shibd_idp}} is the service.
I managed to reproduce this behavior by
* starting shibd_idpw (a.k.a prunmgr.exe)
* modifying Thread Stack Size to be something
* (verify with regedit)
* clear the Thread Stack Size field
* JvmSs is now zero
was:
Just diagnosed an issue with a customer in which the java [process was
unrunnable). This was because {{ HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software
Foundation\Procrun 2.0\shibd_idp\Parameters\Java\JvmSs}} was zero, (where
{{shibd_idp}} is the service.
I managed to reproduce this behavior by
+ starting shibd_idpw (a.k.a prunmgr.exe)
+ modifying Thread Stack Size to be something
+ (verify with regedit)
+ clear the Thread Stack Size field
+ JvmSs is now zero
> Clearing the "Thread Stack Size" field leaves service unstartable
> -
>
> Key: DAEMON-348
> URL: https://issues.apache.org/jira/browse/DAEMON-348
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
>Affects Versions: 1.0.15
> Environment: Windows7 x86
>Reporter: Rod Widdowson
>
> Just diagnosed an issue with a customer in which the java [process was
> unrunnable). This was because {{ HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software
> Foundation\Procrun 2.0\shibd_idp\Parameters\Java\JvmSs}} was zero, (where
> {{shibd_idp}} is the service.
> I managed to reproduce this behavior by
> * starting shibd_idpw (a.k.a prunmgr.exe)
> * modifying Thread Stack Size to be something
> * (verify with regedit)
> * clear the Thread Stack Size field
> * JvmSs is now zero
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DAEMON-348) Clearing the "Thread Stack Size" field leaves service unstartable
Rod Widdowson created DAEMON-348:
Summary: Clearing the "Thread Stack Size" field leaves service
unstartable
Key: DAEMON-348
URL: https://issues.apache.org/jira/browse/DAEMON-348
Project: Commons Daemon
Issue Type: Bug
Components: Procrun
Affects Versions: 1.0.15
Environment: Windows7 x86
Reporter: Rod Widdowson
Just diagnosed an issue with a customer in which the java [process was
unrunnable). This was because {{ HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software
Foundation\Procrun 2.0\shibd_idp\Parameters\Java\JvmSs}} was zero, (where
{{shibd_idp}} is the service.
I managed to reproduce this behavior by
+ starting shibd_idpw (a.k.a prunmgr.exe)
+ modifying Thread Stack Size to be something
+ (verify with regedit)
+ clear the Thread Stack Size field
+ JvmSs is now zero
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DAEMON-329) Can procrun detect the JVM without consulting the registry
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)
