[
https://jira.codehaus.org/browse/SUREFIRE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316922#comment-316922
]
Jesse Glick commented on SUREFIRE-946:
--------------------------------------
Acquiring the lock:
{code:none}
"CommandlineUtils process shutdown hook" prio=10 tid=0x6757a800 nid=0x29b1
waiting for monitor entry [0x678ad000]
java.lang.Thread.State: BLOCKED (on object monitor)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
- waiting to lock <0xa7b292c8> (a
java.lang.UNIXProcess$ProcessPipeOutputStream)
at java.io.FilterOutputStream.close(FilterOutputStream.java:157)
at java.lang.UNIXProcess.destroy(UNIXProcess.java:234)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.CommandLineUtils$ProcessHook.run(CommandLineUtils.java:74)
{code}
Testing fix: I will try to do so soon.
> 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
