org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Software caused connection abort: socket write error

Sonatype JIRA | Harold Shinsato | 7 years ago
  1. 0

    When attempting to upload larger files as SNAPSHOTS to a Nexus repository using mvn deploy:deploy-file, we are seeing a socket error on upload, consistently after about 13.5 minutes. If the file targeted to the same repository location is smaller, there are no problems. Please note that the checksum errors listed in the attached sample files for successful uploads are only showing up because there was a file there previously. The checksum errors did not show up for the first successful SNAPSHOT upload. These errors are not happening for the exact same files and settings when we upload to a Windows based remote file system repository. The maven console says "Error deploying artifact: Software caused connection abort: socket write error". The full trace is in the attachments, but it starts with... [INFO] ------------------------------------------------------------------------ [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Software caused connection abort: socket write error at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) [...] The smalldeploy-file.txt shows the log of a successful upload command: mvn deploy:deploy-file -DgroupId=com.sap.textservices.lx3.lang -DartifactId=tasdk-english-1-0-Dversion=1.1-SNAPSHOT -DuniqueVersion=false -Dpackaging=tar -Dfile=tasdk.tar -DrepositoryId=snapshots -Durl=http://van-s-nsd001.pgdev.sap.corp:1081/nexus/content/repositories/snapshots > smalldeploy-file.txt The deploy-file.txt is the same upload, except with -Dfile=filewith38megabytes.tar, instead of tasdk.tar. Any files can be used as examples, the specific files were altered - so it doesn't seem valuable to try to attache the specific files. Also, our .m2/settings.xml and .m2/settings-security.xml are set up for Nexus security, which obviously we shouldn't send the passwords to a public forum.

    Sonatype JIRA | 7 years ago | Harold Shinsato
    org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Software caused connection abort: socket write error
  2. 0

    When attempting to upload larger files as SNAPSHOTS to a Nexus repository using mvn deploy:deploy-file, we are seeing a socket error on upload, consistently after about 13.5 minutes. If the file targeted to the same repository location is smaller, there are no problems. Please note that the checksum errors listed in the attached sample files for successful uploads are only showing up because there was a file there previously. The checksum errors did not show up for the first successful SNAPSHOT upload. These errors are not happening for the exact same files and settings when we upload to a Windows based remote file system repository. The maven console says "Error deploying artifact: Software caused connection abort: socket write error". The full trace is in the attachments, but it starts with... [INFO] ------------------------------------------------------------------------ [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Software caused connection abort: socket write error at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) [...] The smalldeploy-file.txt shows the log of a successful upload command: mvn deploy:deploy-file -DgroupId=com.sap.textservices.lx3.lang -DartifactId=tasdk-english-1-0-Dversion=1.1-SNAPSHOT -DuniqueVersion=false -Dpackaging=tar -Dfile=tasdk.tar -DrepositoryId=snapshots -Durl=http://van-s-nsd001.pgdev.sap.corp:1081/nexus/content/repositories/snapshots > smalldeploy-file.txt The deploy-file.txt is the same upload, except with -Dfile=filewith38megabytes.tar, instead of tasdk.tar. Any files can be used as examples, the specific files were altered - so it doesn't seem valuable to try to attache the specific files. Also, our .m2/settings.xml and .m2/settings-security.xml are set up for Nexus security, which obviously we shouldn't send the passwords to a public forum.

    Sonatype JIRA | 7 years ago | Harold Shinsato
    org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Software caused connection abort: socket write error
  3. 0

    We run sonar nightly jobs from hudson for all our development and all run at the same time at midnight causing 2 jobs to error. The exact spot in the stacktrace below. [INFO] Sensor SurefireSensor done: 21 ms [INFO] Execute decorators... [INFO] ANALYSIS SUCCESSFUL, you can browse [INFO] Database optimization... [WARN] SQL Error: 1205, SQLState: 40001 [ERROR] Transaction (Process ID 161) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Can not execute Sonar Embedded error: org.hibernate.exception.LockAcquisitionException: could not execute query Transaction (Process ID 161) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute Sonar at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) deadlock with.................................. [INFO] Sensor VersionEventsSensor done: 91 ms [INFO] Sensor SurefireSensor done: 23 ms [INFO] Execute decorators... [INFO] ANALYSIS SUCCESSFUL, you can browse [INFO] Database optimization... [WARN] SQL Error: 1205, SQLState: 40001 [ERROR] Transaction (Process ID 168) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Can not execute Sonar Embedded error: org.hibernate.exception.LockAcquisitionException: could not execute query Transaction (Process ID 168) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute Sonar at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) Any ideas, why does it fail on optimization step? Whats the workaround if any. Thanks

    SonarSource JIRA | 6 years ago | Nandini Obhrai
    org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute Sonar
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Re: Problem with Maven deploy (Error writing to server)

    apache.org | 12 months ago
    org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Error transferring file
  6. 0

    Artifactory / Mailing Lists

    sourceforge.net | 4 months ago
    org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Failed to transfer file: nnotations/3.10.0/gf.annotations-3.10.0.jar. Return code is: 401

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.apache.maven.lifecycle.LifecycleExecutionException

      Error deploying artifact: Software caused connection abort: socket write error

      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals()
    2. Maven Core
      DefaultLifecycleExecutor.executeStandaloneGoal
      1. org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
      2. org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
      2 frames