[jira] [Updated] (DAEMON-348) Clearing the "Thread Stack Size" field leaves service unstartable

2016-05-25 Thread Rod Widdowson (JIRA)

 [ 
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

2016-05-25 Thread Rod Widdowson (JIRA)

 [ 
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)