[
https://issues.apache.org/jira/browse/DAEMON-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
