[
https://jira.codehaus.org/browse/SUREFIRE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316896#comment-316896
]
Jesse Glick commented on SUREFIRE-946:
--------------------------------------
Regardless of why the subprocess is failing to exit, the fact remains that the
current {{ProcessHook}} tries to acquire a lock during a shutdown hook with no
timeout and no guarantee that this lock will be released in a timely fashion.
Making it more likely for the subprocess to exit cleanly may make this bug
less likely to occur but will not completely prevent it. Supplementing Andreas
fix with a patch to {{ProcessHook}} to impose a timeout on the call to
{{Process.destroy}} still seems like a good idea.
> Maven hangs on SIGTERM when using Surefire forking
> (CommandLineUtils.ProcessHook)
> ---------------------------------------------------------------------------------
>
> Key: SUREFIRE-946
> URL: https://jira.codehaus.org/browse/SUREFIRE-946
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Jesse Glick
> Attachments: stack.txt, SUREFIRE-946.patch
>
>
> Java 7u7, Surefire with JUnit {{forkMode="perthread"}} + {{threadCount="1"}}
> + {{reuseForks="true"}}. After pressing Ctrl-C to stop the Maven test run,
> the process hangs and must be killed with SIGKILL. From the thread dump,
> {{CommandLineUtils.ProcessHook}} and {{StreamFeeder}} look responsible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
