You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "K.C. Baltz (JIRA)" <ji...@codehaus.org> on 2005/11/18 18:55:06 UTC
[jira] Commented: (MNG-678) scp intermittently failing deploying artifact
[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_51352 ]
K.C. Baltz commented on MNG-678:
--------------------------------
I was doing more testing with sftp and the "session is down" issue and I found a possible clue. I can get sftp deployment to work when I'm connecting to a Solaris 10 system, but not Solaris 9. I'm sending to the same directory because my home directory is mounted on any host to which I log in. Perhaps there's a difference in the ssh/sftp implementations on the two systems.
> scp intermittently failing deploying artifact
> ---------------------------------------------
>
> Key: MNG-678
> URL: http://jira.codehaus.org/browse/MNG-678
> Project: Maven 2
> Type: Bug
> Components: maven-artifact
> Versions: 2.0-alpha-3
> Environment: JDK 1.5, Red Hat 9
> Reporter: Joe Futrelle
> Assignee: Brett Porter
> Fix For: 2.0.1
>
>
> 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 why.
> 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://chasm.ncsa.uiuc.edu//home/futrelle/m2/repository
> at org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:331)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:167)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:91)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:73)
> ... 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(ScpWagon.java:271)
> ... 20 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org