Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44857

ERROR: Aborted Maven execution for InterruptedIOException java.net.SocketTimeoutException: Accept timed out

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None

      -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

          ikedam added a comment -

          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.

          ikedam added a comment - 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.

          I have added the complete stacktrace. Any help would be appreciated. Thank you!

          Jean Paul Larach added a comment - I have added the complete stacktrace. Any help would be appreciated. Thank you!

          ikedam added a comment -

          Looks an issue of maven-plugin.

          ikedam added a comment - Looks an issue of maven-plugin.

          Oleg Nenashev added a comment -

          Timeout can be changed via System Property: https://github.com/jenkinsci/maven-plugin/blob/master/src/main/java/hudson/maven/MavenProcessFactory.java#L188

          If Maven startup takes long due to whatever reason, it could help

          Oleg Nenashev added a comment - Timeout can be changed via System Property: https://github.com/jenkinsci/maven-plugin/blob/master/src/main/java/hudson/maven/MavenProcessFactory.java#L188 If Maven startup takes long due to whatever reason, it could help

          Hello Oleg! I actually installed the Naginator plugin which restarts a build after Fail or Abort. So far the builds have not timed out at all. I am still testing the plugin as a possible solution but if that fails I will definitely look at changing the timeout system property. Thanks for your help!

          Jean Paul Larach added a comment - Hello Oleg! I actually installed the Naginator plugin which restarts a build after Fail or Abort. So far the builds have not timed out at all. I am still testing the plugin as a possible solution but if that fails I will definitely look at changing the timeout system property. Thanks for your help!

            Unassigned Unassigned
            jlara005 Jean Paul Larach
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: