[
https://issues.apache.org/jira/browse/DAEMON-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039373#comment-18039373
]
Mark Thomas commented on DAEMON-469:
------------------------------------
If the previous start happened less than 60s before the JVM aborted, jsvc will
wait for 60s before attempting to restart the JVM to avoid looping.
Those numbers don't seem unreasonable to me. If the service aborts within 60s
of starting it is very likely to abort within 60s of the restart.
I'm currently leaning towards resolving this as "won't fix".
> Restart on OOM
> --------------
>
> Key: DAEMON-469
> URL: https://issues.apache.org/jira/browse/DAEMON-469
> Project: Commons Daemon
> Issue Type: New Feature
> Components: Jsvc
> Reporter: Lapo Luchini
> Priority: Major
>
> {{jsvc}} should have a way to restart on {{java -XX:+ExitOnOutOfMemoryError}}
> which returns with status 3, not 123 as expected.
> Maybe an extra configuration parameter, or simply supporting both 3 and 123
> as requests for restarts?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
