[
https://issues.apache.org/jira/browse/MSHARED-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17374490#comment-17374490
]
Alexander Kriegisch commented on MSHARED-867:
---------------------------------------------
I have a similar case in an integration test from the Maven Surefire project,
see [here|https://github.com/apache/maven-surefire/pull/355] for more details
and a reproducer. In this case, Failsafe runs the test, not Invoker. But for
process execution, also Maven Shared Utils 3.1.0 is used, so this is probably
the same issue. It would be nice if you could take a look.
Attention: The linked PR as such does not reproduce the problem, but the branch
mentioned there, porting back the IT to a state before a certain Surefire bug
was fixed, reproduces the problem. It was simply meant to verify that the same
test would successfully terminate all child processes in case of a hanging test
JVM. Unexpectedly, I reproducibly found leftover console and Java processes, at
least on Windows (did not check other OS types yet). So I investigated if this
is a known problem and found this issue.
> Timed out processes can stay alive in background
> ------------------------------------------------
>
> Key: MSHARED-867
> URL: https://issues.apache.org/jira/browse/MSHARED-867
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-invoker
> Affects Versions: maven-invoker-3.0.1
> Environment: Windows, Java 8
> Reporter: Robert Scholte
> Priority: Major
>
> MSHARED-795 introduced a timeout for processes, but on Windows I can see Java
> processes staying alive, Maven Invoker just continues without forcing them to
> stop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
