[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_48348 ]
Ørjan Austvold commented on MNG-678:
------------------------------------
A new version of jsch has just been released (0.1.23).
Changes since version 0.1.22:
- bugfix: there is a freeze problem at fails on key-exchanging. FIXED.
- bugfix: race-condition forcefully disconnects session in closing channels.
FIXED.
Could the "freeze" bugfix be releated to the scp knowhosts tests failing?
Here's what was reported on sch-mailinglist:
Hi,
+-From: Michal Belicek <[EMAIL PROTECTED]> --
|_Date: Fri, 07 Oct 2005 14:24:11 +0200 __
|
|I have found one bug in jsch-0.1.22. The thing is that, when calling
|session.connect() and the call checkHost(host, kex) inside of the
|connect(...) method in Session.java throws JSchException, then the
|program will freeze on line 432: write(packet) because of infinite loop.
|The fix is following:
|diff Session.java Session_.java
|426a427
|>> in_kex = false;
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
