This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 174949 - [terminal-ssh] ssh connection fails with "Session.connect: java.io.IOException: End of IO Stream Read"
Summary: [terminal-ssh] ssh connection fails with "Session.connect: java.io.IOExceptio...
Status: RESOLVED DUPLICATE of bug 174953
Alias: None
Product: Target Management
Classification: Tools
Component: Terminal (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 2.0   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-21 07:54 EST by Martin Oberhuber CLA
Modified: 2008-08-13 13:16 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-02-21 07:54:34 EST 
Ssh homedir is set for private-key authentication without passphrase.
Connect RSE ssh to build.eclipse.org works without password.

Trying to connect terminal-ssh without password brings up an "enter password"
dialog, then the following is printed to the Terminal:
Session.connect: java.io.IOException: End of IO Stream Read

Ssh timeout is set to 60.
Multiple terminals are open, connection is tried in the first one.

-----------Enter bugs above this line-----------
TM 2.0M5 Testing
installation : eclipse-SDK-3.3M5 (I20070209-1006), cdt-4.0M5, emf-2.3M5
RSE install  : RSE-SDK I20070219-1645 + discovery + efs
java.runtime : Sun 1.4.2_13
os.name:     : Windows XP 5.1, Service Pack 1
------------------------------------------------
systemtype   : Unix-ssh / Linux-dstore-processes
targetos     : Red Hat Enterprise Linux WS release 4 (Nahant Update 3)
targetuname  : Linux parser.takefive.co.at 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 athlon i386 GNU/Linux
targetvm     : Sun Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
------------------------------------------------
Comment 1 Martin Oberhuber CLA 2007-02-21 08:00:29 EST 
The problem seems to be that if the connection failed once, it will consistently fail all the time. In the concrete case, I had seen the "Host authenticity can not be established" dialog and not answered it for 60 seconds (connection timeout). It looks like this was sufficient to bring the current terminal instance in a state where it simply does not work any more.

The problems I can see are:
1. Ssh homedir is not correctly fetched from the Preferences. 
2. The jsch instance is not shared between Terminals and RSE, since I can 
   connect correctly in Terminal B but it consistently fails in Terminal A.
3. The timeout seems not to be applied correctly. "Network timeout" from the 
   Preferences should be the default (bug 174951)
4. Sessions that failed due to timeout are not cleaned up correctly.
5. Sessions are not re-used. There should be a simple session cache as long
   as there are multiple connections to the same host.
Comment 2 Martin Oberhuber CLA 2007-02-21 08:07:38 EST 
This might actually be a duplicate of bug 174953 so it would work as soon as that one is fixed.
Comment 3 Martin Oberhuber CLA 2007-05-30 08:35:51 EDT 
Works as per 2.0RC1, so this is presumably a duplicate of bug #174953.

*** This bug has been marked as a duplicate of bug 174953 ***
Comment 4 Martin Oberhuber CLA 2008-08-13 13:16:50 EDT 
[target cleanup] 2.0 M5 was the original target milestone for this bug