Re: [JSch-users] Unsupported type 92
Status: Alpha
Brought to you by:
ymnk
From: Frank B. <li...@be...> - 2004-06-29 08:29:02
|
Hi, On Tue, 29 Jun 2004 12:37:41 +0900 ym...@jc... (Atsuhiko Yamanaka) wrote: > +-From: "B. Scott Smith" <sc...@sm...> -- > |_Date: Mon, 28 Jun 2004 23:13:58 -0400 ___________ > | > |Hi all, I am occasionally getting the following error using Jsch > |against a Cygwin sshd on Windows 2000: > | > | Session.run: unsupported type 92 > | > |I see this is defined as: SSH_MSG_CHANNEL_OPEN_FAILURE, and is, in > |fact, not one of the message types checked. > | > |When I see this error, my application will not exit - I assume > |this is because of a dangling Session Thread. Any ideas? Is > |anyone else seeing this error? I got the same problem in a program where I use JSch to tunnel a connection to a database server: <code> channel = session.openChannel("direct-tcpip"); System.out.println("1"); in = ((ChannelDirectTCPIP)channel).getInputStream(); out = ((ChannelDirectTCPIP)channel).getOutputStream(); ((ChannelDirectTCPIP)channel).setHost(mySQLHost); ((ChannelDirectTCPIP)channel).setPort(mySQLPort); System.out.println("2"); channel.connect(); System.out.println("3"); </code> It hangs after "2" with "Session.run: unsupported type 92" if the mySQLHost gives a connection refused error or doesn't answer (connection times out). > How about trying http://www.jcraft.com/jsch/jsch-0.1.16-rc5.zip ? This fixes it only partly. Now all steps are passed though "channel.connect()" - understandably - takes very long in the second case (connection times out) but I get a "java.io.EOFException, underlying cause: null" later (where I cannot catch it) which is bad IMO. It would be nice if "channel.connect();" would throw an Exception showing that something went wrong. Best regards and TIA Frank Benkstein. |