[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_52533 ] 

Michael Fiedler commented on MNG-678:
-------------------------------------

I am getting this error again.  I used ssh-keygen to make a private & public 
file to get around the deploy hanging.

I am using maven2 when I ran release:deploy on a win xp, sp2 machine to a w2k 
host via OpenSSH.

My project structure is:
modules
 - util
 - exceptions
 - modC
 - modD

I was able to get the following files uploaded before the error:
[INFO] [deploy:deploy]
host - private computer system & equipment: Uploading: 
scp://host/com/werner/modules/1.0-QA/modules-1.0-QA.pom
...
host - private computer system & equipment: host - private computer system & 
equipment: Uploading: 
scp://host/com/werner/modules/1.0-QA/modules-1.0-QA-javadoc.pom
...
[INFO] [deploy:deploy]
host - private computer system & equipment: Uploading: 
scp://host/com/werner/util/1.0-QA/util-1.0-QA.jar
...
host - private computer system & equipment: host - private computer system & 
equipment: Uploading: scp://host/com/werner/util/1.0-QA/util-1.0-QA-javadoc.jar
...
host - private computer system & equipment: Uploading: 
scp://host/com/werner/util/1.0-QA/util-1.0-QA-sources.jar
...
[INFO] [deploy:deploy]
host - private computer system & equipment: Uploading: 
scp://host/com/werner/exception/1.0-QA/exception-1.0-QA.jar
...
67K uploaded
[INFO] Retrieving previous metadata from M2_repo
host - private computer system & equipment: [INFO] Uploading repository 
metadata for: 'artifact com.werner:exception'
host - private computer system & equipment: [INFO] 
----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] 
----------------------------------------------------------------------------
[INFO] Error installing artifact's metadata: Error while deploying metadata: 
Did receive proper ACK: '1'


Thank you, Michael



> scp intermittently failing deploying artifact
> ---------------------------------------------
>
>          Key: MNG-678
>          URL: http://jira.codehaus.org/browse/MNG-678
>      Project: Maven 2
>         Type: Bug
>   Components: Artifacts and Repositories
>     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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to