As far as I can tell we are cleaning up all the connections properly. I'd need to research the issue, but since m2 runs in a new JVM each time I'd be surprised if that was the cause.
Can you fiela bug in JIRA for investigation? Thanks, Brett On 7/29/05, Joe Futrelle <[EMAIL PROTECTED]> wrote: > Not sure if this has been reported before, but some of the time > deploying artifacts fails during the scp transfer. The bottom of the > stack trace is reproduced below. This is with Maven 2 alpha 3 and JDK > 1.5 under Red Hat 9. 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. > > 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 > > -- > Joe Futrelle > Digital Library Technologies, NCSA > http://www.ncsa.uiuc.edu/People/futrelle > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
