Re: [Beepcore-java-users] Bing and Beepd lock on large messages

[Huston <hu...@us...>]

> 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.

The problem was that the IO thread was being used for the message
notifications. If the profile used this thread to process the message then
SEQs would not be processed.  This has been fixed in cvs.

> > 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 just tried the latest source in cvs and it doesn't seem to have the
problem.

--Huston