[
https://issues.apache.org/jira/browse/SUREFIRE-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961484#comment-15961484
]
Hudson commented on SUREFIRE-1357:
----------------------------------
UNSTABLE: Integrated in Jenkins build maven-surefire #1690 (See
[https://builds.apache.org/job/maven-surefire/1690/])
[SUREFIRE-1357] PING scheduler kills JVM in debug mode (tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=eed317207695e3174d2f283390dd0386fc09f3e4])
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ForkClient.java
> PING scheduler kills JVM in debug mode
> --------------------------------------
>
> Key: SUREFIRE-1357
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1357
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Fix For: 2.20
>
>
> This issue was found during second Vote of Version 2.20.
> Configuration parameter {{debugForkedProcess=true}} kills the JVM because all
> threads are disabled for scheduling purposes and PING scheduler suggested
> killing JVM when developer stepped into a break point after 20 seconds.
> The dump file contains error
> {{Corrupted stdin stream in forked JVM 1. Stream 'Listening for transport
> dt_socket at address: 5005'.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
