maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Moved: (WAGON-190) scp intermittently failing deploying artifact
Date Wed, 14 May 2008 07:37:29 GMT


Brett Porter moved WAGONSSH-28 to WAGON-190:

    Fix Version/s:     (was: 1.0-alpha-6)
      Component/s:     (was: wagon-ssh)
              Key: WAGON-190  (was: WAGONSSH-28)
          Project: Maven Wagon  (was: wagon-ssh)

> scp intermittently failing deploying artifact
> ---------------------------------------------
>                 Key: WAGON-190
>                 URL:
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-ssh
>         Environment: JDK 1.5, Red Hat 9
>            Reporter: Joe Futrelle
>            Assignee: Brett Porter
>             Fix For: 1.0-alpha-6
> Some of the time, deploying artifacts fails during the scp transfer. The bottom of the
stack trace is reproduced below. If I run the m2 deploy enough times, it succeeds; not sure
> This is not an unknown issue with Jsch; apparently client code can cause behavior like
this if it doesn't dispose of connections properly. Possibly a plugin that's runs before the
deploy phase is messing up the connection state somehow?
> Caused by: org.apache.maven.wagon.TransferFailedException: Error occured while deploying
'ncsa/gsbt/1.0-SNAPSHOT/gsbt-1.0-20050728.190330-38.pom.sha1' to remote repository: scp://
>         at org.apache.maven.wagon.providers.ssh.ScpWagon.put(
>         at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
>         at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(
>         at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(
>         ... 17 more
> Caused by: com.jcraft.jsch.JSchException: session is down
>         at com.jcraft.jsch.Channel.connect(Unknown Source)
>         at org.apache.maven.wagon.providers.ssh.ScpWagon.put(
>         ... 20 more

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message