I hit this before and actually posted a bug, which has since been closed.
Dunno if I agree with the resolution, but it's actually a known "behavior".
The problem is that the channel chokes when the window closes down and can't
process SEQ frames.
Take a look for the bug on Sourceforge under all bugs, not just open ones
and you'll get the whole blow-by-blow.
The short answer for the moment is make sure your messages get passed
off to another thread to get handled/read, so that the "core" channel
management stuff does not get blocked by your read which is trying to read
the complete message. If you make that extra thread it works like a charm.
-bill
On Wed, Jun 12, 2002 at 06:31:03PM -0700, Zed A. Shaw wrote:
> Hey,
>
> I just posted this to the forum before I found the list. You can ignore the
> forum message if you like.
>
> I'm seeing some strange behavior when the size of a message is greater than
> 4096. If I set the size for Bing to 4097, it sends a bit, then chokes and
> sits there. If I set it extremely high (like 7000), it sends some, the
> server responds some, and then the client chokes and does nothing.
>
> I did a protocol analysis, and it looks like there's something wrong with
> how Bing is reading the replies. Any clues? I'm interested in file
> transfers, so sending in 4K chunks and having the library hang on anything
> large will not do. Any help is appreciated.
>
>
> --
> Zed A. Shaw
>
>
>
>
> _______________________________________________________________
>
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> Beepcore-java-users mailing list
> Bee...@li...
> https://lists.sourceforge.net/lists/listinfo/beepcore-java-users
|
