> SOmeone else mentioned the problem with beecore-java stalling
> on large RPY's. My hunch, unconfirmed, is that the threading
> model is more in flux than first suspoected, as evidenced by the
> Echo profile needing to be reverted.
There haven't been any changes to the threading model added to cvs since the
last release, I only started the threading changes in late December so from
the dates in cvs you can verify this. I found a bug in the InputDataStream
while working on the threading changes. The bug was significant enough I
wanted to add it before the new threading model was finished. I just made a
mistake with EchoProfile.java and checked in the wrong version.
> With the Echo profile handling it's own thread management and the
> main thread free to read on teh socket and process SEQ's it seems
> to be working fine. I'd suggest having the profile start create
> it's own worker thread to process the receiveMSG calls (hand them
> off with a queue or something) and I bet the stalling bug goes away.
This has been the requirement since the first release of beepcore-java. The
new threading model I am working on will remove this requirement.
--Huston
|
