Hi,
+-From: Anand Vaidya <[EMAIL PROTECTED]> --
|_Date: Thu, 13 Mar 2008 11:24:49 +0800 __________
|
|There is a FAQ at Trilead (
|http://www.trilead.com/Products/Trilead-SSH-2-Java/FAQ/ ). Which talks
|about the need to read STDOUT and STDERR simultaneously, else one of them
|(STDERR, usually) will cause the session to hang. I will not repeat the
|details here. The problem seems to affect the session when there is a
|large quantity of outputs on stderr.
I have not checked that FAQ, but I guess that problem will also occur on jsch,
because it has come from the design of SSH2 protocol.
The STDOUT and STDERR(SSH_MSG_CHANNEL_DATA and SSH_MSG_CHANNEL_EXTENDED_DATA)
have shared the same window for packets.
|They have implemented a StreamGobbler class which consumed returned bytes
|from remote system STDOUT and STDERR.
|I would like to know whether JSCH also faces such issues and what is the
|implemented or planned solution.
I think that the only solution for this issue must be to read
STDOUT and STDERR earnestly and simultaneously. I guess that class
has implemented this solution.
As for the plan,....
I think that users will be able to implement such a class easily,
and also the user-land program will be able to work around
such an issue without such a class by their logic.
So, I have not planed in this time.
Any suggestions are welcome.
Sincerely,
--
Atsuhiko Yamanaka
JCraft,Inc.
1-14-20 HONCHO AOBA-KU,
SENDAI, MIYAGI 980-0014 Japan.
Tel +81-22-723-2150
+1-415-578-3454
Fax +81-22-224-8773
Skype callto://jcraft/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
JSch-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users
