-We have a nightly build that runs at 7pm everyday. Sometimes the build runs successfully and sometimes the build aborts due to a "SocketTimeout" issue. I have seen some tickets with this same issue and none have a resolution. Please advise:
-"ERROR: Aborted Maven execution for InterruptedIOException
java.net.SocketTimeoutException: Accept timed out"
-I have also tried setting the "-Djava.net.preferIPv4Stack=true" but it didn't work
-This also happens after you reboot the machine and you first try to run any of the builds.
COMPLETE STACKTRACE:
ERROR: Aborted Maven execution for InterruptedIOException
java.net.SocketTimeoutException: Accept timed out
at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
at java.net.DualStackPlainSocketImpl.SocketAccept(DualStackPlainSocketImpl.java:135)
at java.net.AbstractPlainSocketImpl.accept(PlainSocketImpl.java:199)
at java.net.ServerSocket.implAccept(ServerSocket.java:530)
at java.net.ServerSocket.accept(ServerSocket.java:498)
at Hudson.maven.AbstractMavenProcessFactory$SocketHandler$AcceptorImpl.accept
(AbstractMavenProcessFactory.java:213)
at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:282)
at hudson.maven.ProcessCache.get(ProcessCache.java:236)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:798)
at hudson.maven.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1728)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Archiving artifacts
Started calculate disk usage of build
Finished calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished calculation of disk usage of workspace in 0 seconds
Finished: ABORTED
[JENKINS-44857] ERROR: Aborted Maven execution for InterruptedIOException java.net.SocketTimeoutException: Accept timed out
Component/s | New: core [ 15593 ] | |
Component/s | Original: build-pipeline-plugin [ 15962 ] | |
Component/s | Original: build-timeout-plugin [ 15530 ] | |
Component/s | Original: clearcase-plugin [ 15503 ] | |
Component/s | Original: envinject-plugin [ 15893 ] | |
Component/s | Original: maven-plugin [ 16033 ] | |
Component/s | Original: next-executions-plugin [ 15996 ] | |
Component/s | Original: pipeline [ 21692 ] | |
Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] | New: Jean Paul Larach [ jlara005 ] |
Description |
Original:
-We have a nightly build that runs at 7pm everyday. Sometimes the build runs successfully and sometimes the build aborts due to a "SocketTimeout" issue. I have seen some tickets with this same issue and none have a resolution. Please advise: -"ERROR: Aborted Maven execution for InterruptedIOException java.net.SocketTimeoutException: Accept timed out" -I have also tried setting the "-Djava.net.preferIPv4Stack=true" but it didn't work -This also happens after you reboot the machine and you first try to run any of the builds. |
New:
-We have a nightly build that runs at 7pm everyday. Sometimes the build runs successfully and sometimes the build aborts due to a "SocketTimeout" issue. I have seen some tickets with this same issue and none have a resolution. Please advise: -"ERROR: Aborted Maven execution for InterruptedIOException java.net.SocketTimeoutException: Accept timed out" -I have also tried setting the "-Djava.net.preferIPv4Stack=true" but it didn't work -This also happens after you reboot the machine and you first try to run any of the builds. COMPLETE STACKTRACE: ERROR: Aborted Maven execution for InterruptedIOException java.net.SocketTimeoutException: Accept timed out at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method) at java.net.DualStackPlainSocketImpl.SocketAccept(DualStackPlainSocketImpl.java:135) at java.net.AbstractPlainSocketImpl.accept(PlainSocketImpl.java:199) at java.net.ServerSocket.implAccept(ServerSocket.java:530) at java.net.ServerSocket.accept(ServerSocket.java:498) at Hudson.maven.AbstractMavenProcessFactory$SocketHandler$AcceptorImpl.accept (AbstractMavenProcessFactory.java:213) at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:282) at hudson.maven.ProcessCache.get(ProcessCache.java:236) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:798) at hudson.maven.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1728) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Archiving artifacts Started calculate disk usage of build Finished calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished calculation of disk usage of workspace in 0 seconds Finished: ABORTED |
Assignee | Original: Jean Paul Larach [ jlara005 ] |
Component/s | New: maven-plugin [ 16033 ] | |
Component/s | Original: core [ 15593 ] |
It doesn't sounds like an issue of a specific plugin (Rather it sounds like an environmental issue to me).
Please attach whole the console log and the system log when the build failed.