If you're using scheduled jobs that's actually another problem as
documented here http://jira.red5.org/browse/APPSERVER-10 .
Basically after a period of running, the scheduler locks up all the
threads available to it preventing you from doing further scheduling
and preventing the server from doing processes it needs to as well.
One of the problem areas of code was removed during a recent revision
but the underlying problem is still there.
--Dan--
On Apr 4, 2007, at 11:18 AM, Tom Krcha wrote:
Hi,
I have just tested latest trunk and connections lockup problem is
still there.
You can make a robot which will send messages to server in short
interval. Run about 20 of robots and it freezes.
Bad :(
T.
2007/4/4, Daniel Daley <[EMAIL PROTECTED]>:
Mina 2 caused connection lockups to occur until the server became
unresponsive. You can look at http://jira.red5.org/browse/
APPSERVER-41 for more information.
--Dan--
On Apr 4, 2007, at 6:20 AM, nomIad wrote:
> Hi,
>
> Was there a reason to backport red5 to mina 1.0.1?
> And is there any things we have to mention in our old apps?
>
> mfg nomiad?
>
> _______________________________________________
> Red5 mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/red5_osflash.org
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
