You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2022/08/08 14:25:00 UTC

[jira] [Updated] (OAK-9849) Add log message if oak-run is terminated from externally

     [ https://issues.apache.org/jira/browse/OAK-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joerg Hoh updated OAK-9849:
---------------------------
    Description: 
We have a case where we run oak-run under the control the linux "timeout" tool, which sends a SIGTERM signal when the timeout has passed. Currently this terminates the JVM without any indication from within oak-run itself.

in this situation oak-run should print a statement "terminated by external signal" to stderr. 
Also it should be possible to instruct oak-run to print a threaddump in such situations. With this it should be possible to see at which point the execution was.

  was:
We have a case where we run oak-run under the control the linux "timeout" tool, which sends a SIGTERM signal when the timeout has passed. Currently this terminates the JVM without any indication from within oak-run itself.

in this situation oak-run should print a statement "terminated by external signal" to stderr.



> Add log message if oak-run is terminated from externally
> --------------------------------------------------------
>
>                 Key: OAK-9849
>                 URL: https://issues.apache.org/jira/browse/OAK-9849
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: oak-run
>    Affects Versions: 1.44.0
>            Reporter: Joerg Hoh
>            Assignee: Joerg Hoh
>            Priority: Major
>
> We have a case where we run oak-run under the control the linux "timeout" tool, which sends a SIGTERM signal when the timeout has passed. Currently this terminates the JVM without any indication from within oak-run itself.
> in this situation oak-run should print a statement "terminated by external signal" to stderr. 
> Also it should be possible to instruct oak-run to print a threaddump in such situations. With this it should be possible to see at which point the execution was.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)