Helo,
I have fresh news, about this bug. If I use the Beepd.java as listener,
I have no problems, no bugs. But, if I put my listener into the Phoenix
4.0a4 framework as application (.sar file) this bugs still appears even
when I'm simply using only the Bing.java.
We have an application server build on Avalon Phoenix which uses BEEP as
communication protocol.
I suspect that there are some problems with threading and
synchronization, which makes BEEP give those particular errors I was
mentioning.
Are there any restrictions on working with threads in regard with BEEP ?
I have to mention that we had it working almost perfectly with an older
version of BEEP (about a year old :) so these problems are new to us.
atech
|
