Hello Atsuhiko,
> You know that OpenSSH's sshd allows to open 10 "shell" and "exec"
> channels simultaneously, and on such a case it will send back that
> message with SSH_OPEN_ADMINISTRATIVELY_PROHIBITED(1).
>
> try{
> channel.connect();
> }
> catch(JSchException e){
> if(channel.getExitStatus()==1){
> // SSH_OPEN_ADMINISTRATIVELY_PROHIBITED
> }
> }
That code does not work with Jsch-0.1.36 against an
OpenSSH_3.9p1 server. The exception is not being thrown.
Instead, when I later try to write to an OutputStream
attached to the Channel, JSch throws an IOException
("failed to initialize the channel") in Channel.java
line 269.
That exception, however, is cought away by the Stream
which closes automatically -- so I get no indication at
all that I was unable to open the channel.
If you have Eclipse DSDP-TM / RSE, the issue is rather
simple to reproduce: just launch 11 shells on a single
connection. The 11th shell does not connect. See also
https://bugs.eclipse.org/bugs/show_bug.cgi?id=209043
The developer of our own SSH Server said: "The issue is
to some extent caused by the Eclipse Jsch client sending
a channel request for which it does not request a response.
Therefore IPSSH does not notify the ssh client of the failed
request. (RFC 4253 states "It is RECOMMENDED that the reply
to these messages be requested and checked")."
What do you think is going wrong here?
Thanks,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
JSch-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users
