I am just wondering if you were able to understand the issue I was encountering
here with the initial window size at 1048576, where the max data that is
allowed to come back from an SSHExec call was fixed at this number before the
channel was closed. If need be I can try to come up with an example to
demonstrate the issue.
--- On Wed, 6/4/08, Atsuhiko Yamanaka <[EMAIL PROTECTED]> wrote:
> From: Atsuhiko Yamanaka <[EMAIL PROTECTED]>
> Subject: Re: [JSch-users] initial window size fixed...
> To: [EMAIL PROTECTED]
> Cc: jsch-users@lists.sourceforge.net
> Date: Wednesday, June 4, 2008, 9:55 PM
> Hi,
>
> +-From: Bubba Meetze <[EMAIL PROTECTED]> -------
> |_Date: Thu, 29 May 2008 17:51:32 -0700 (PDT) __
> |
> |I was running into a problem where my data coming back
> |from an SSHExec session was getting limited to 1048576
> |bytes, then I realized that what I was hitting was the
> |initial window size that is fixed in the Channel.java
> |code.
>
> What kind of failure do you have, by the fixed window size?
> That window size is for the packet pool and
> that pool has been be used for the flow control.
> Is your concern related to the packet size from the remote?
>
> 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/
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users
