[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_52068 ]
Bart Selders commented on MNG-678: ---------------------------------- I "was" also affected by this "session is down" problem. It just started at once, no explanation, while it used to work fine before. For us, it turned out to be a DNS problem: in this case primary DNS server down, the repository server was resolving network addresses using its secondary DNS server. We did not notice it that quick, although some other things did not work as fast as well. After correcting this, everything turned back to normal, and scp deployment works fine again. I am not suggesting that this is the root cause for this issue, but i would at least recommend to investigate your network to see whether there are any network issues known. > 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]
