Luiz, In order to find the root cause of this issue, I think we'd better have a test case to reproduce it. Is it possible for you to provide a test scenario that could possibly reproduce this freezing? Maybe you can describe what you have done with SOs in your application and I will try to write a case.
On 4/23/07, Luiz Filipe <[EMAIL PROTECTED]> wrote:
Hey guys, how´re doing. I just let you know that Red5 keeps freezing after 24hours with 300 simultaneous connected users. We have tried several approaches, like disable ghost connections, increase server memory and cpu, and others, but neither solved this problem. As our project is a typical card game application, we´re using sharedObjects on client and server to hold connected users, game rooms, who is on these game rooms, game methods based on so.send and so one. We´re thinking to change all our SharedObjects engine approach to NetConnections call´s, because that freeze problem is related with SO´s and maybe because using so´s on a large card game project isn´t the best solution. Do you guys have another opinion about that ? Thanks a lot for any help. Best Regards, Luiz Filipe. _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
-- I cannot tell why this heart languishes in silence. It is for small needs it never asks, or knows or remembers. -- Tagore Best Regards Steven Gong
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
