You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2024/10/17 16:48:00 UTC

[jira] [Comment Edited] (EXEC-123) Child processes not getting killed

    [ https://issues.apache.org/jira/browse/EXEC-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890512#comment-17890512 ] 

Gary D. Gregory edited comment on EXEC-123 at 10/17/24 4:47 PM:
----------------------------------------------------------------

Raising the Java platform requirement is worth discussing on the mailing list, I'll start a thread. I discuss raising it to the next LTS level: Java 11.


was (Author: garydgregory):
Rasing the Java platform requirement is worth discussing on the mailing list, I'll start a thread.

> Child processes not getting killed
> ----------------------------------
>
>                 Key: EXEC-123
>                 URL: https://issues.apache.org/jira/browse/EXEC-123
>             Project: Commons Exec
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Wolff Bock von Wuelfingen
>            Priority: Major
>
> While searching for something completely different related to Commons Exec, i found this:
> [https://stackoverflow.com/questions/35601924/java-apache-commons-exec-watchdog-and-windows-cmd-exe-issues]
> The answer there uses `Process.descendants()` to also kill the child processes. That method was added with Java 9.
> Since this problem is important enough to be one of the five [FAQ questions|https://commons.apache.org/proper/commons-exec/faq.html], i think it might be a good idea to raise the minimum Java version of Commons Exec and use the `descendants()` method to fix that problem.



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