maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <>
Subject [jira] [Commented] (SUREFIRE-1374) std/in stream corrupted error
Date Sat, 14 Oct 2017 18:50:00 GMT


Tibor Digana commented on SUREFIRE-1374:

I found your problem was reported in
In both issues your tests do not fail due to this. Please contact vendors of your dependencies
and try to configure a logger. We start {{ForkedBooter#main()}} then we call {{System.setOut()}}
and then we run JUnit core. If SpringBoot or some other dependencies scans classpath and reads
and caches {{System.out}} before we override it with our wrapper then you will see the log
in console. If you use version {{2.20.1}} this log appears just once on Maven console, at
least I hope. The dump will print it always. So it should not be much annoying but the annoying
is the frameworks which should be better configured or better cache {{System.out}} on first
call of logger and not on the application startup.

> std/in stream corrupted error
> -----------------------------
>                 Key: SUREFIRE-1374
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.20
>            Reporter: matteo rulli
>            Assignee: Tibor Digana
> We bumbed surefire version to 2.20 (from 2.19.1) and our tests started generating this
kind of errors:
> {code}
> # Created on 2017-05-26T10:24:04.032
> [SUREFIRE] std/in stream corrupted
> Command BYE_ACK unexpectedly read Void data with length 4.
> 	at org.apache.maven.surefire.booter.MasterProcessCommand.decode(
> 	at org.apache.maven.surefire.booter.CommandReader$
> 	at
> {code}
> Related stacktrace:
> {code}
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: Error occurred
in starting fork, check output in log
> [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(
> [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(
> [ERROR] 	at
> [ERROR] 	at
> [ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(
> [ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(
> [ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(
> [ERROR] 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
> [ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> [ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> [ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> [ERROR] 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
> [ERROR] 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
> [ERROR] 	at
> [ERROR] 	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(
> [ERROR] 	at org.apache.maven.DefaultMaven.doExecute(
> [ERROR] 	at org.apache.maven.DefaultMaven.doExecute(
> [ERROR] 	at org.apache.maven.DefaultMaven.execute(
> [ERROR] 	at org.apache.maven.cli.MavenCli.execute(
> [ERROR] 	at org.apache.maven.cli.MavenCli.doMain(
> [ERROR] 	at org.apache.maven.cli.MavenCli.main(
> [ERROR] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> [ERROR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> [ERROR] 	at java.lang.reflect.Method.invoke(
> [ERROR] 	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
> [ERROR] 	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
> [ERROR] 	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
> [ERROR] 	at org.codehaus.plexus.classworlds.launcher.Launcher.main(
> [
> {code}
> Everything worked fine with 2.19.1.
> Environment: macOS sierra, java version "1.8.0_74", Apache Maven 3.5.0  

This message was sent by Atlassian JIRA

View raw message