Luiz, Are you sure that the threads you need exceed 16? I've updated the trunk to take a new property maxEventThreads and the default value is 128. You can try your application again. Thanks.
On 5/3/07, Luiz Filipe <[EMAIL PROTECTED]> wrote:
Hi Luke, The first thing that we already detected in this new changes is that the new propertie "rtmp.event_threads" on red5.properties didn´t have any effect on the number of threads been executing. We changed this propertie to "32" and our highest thread number is always 16. ([DEBUG] 4407222 AnonymousIoService-16) Thanks, Luiz Filipe. -----Mensagem original----- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nome de Luiz Filipe Enviada em: quinta-feira, 3 de maio de 2007 01:38 Para: [email protected] Assunto: [Red5] RES: [Fwd: [Red5devs] Changed to Mina 1.1, and other changes.] Hi Joachim, how´re doing. Just minuts ago we´ve update our server with the latest version from trunk, let´s see this news changes in action. Any good or bad news i let you know. Luke and Joachim, thanks a lot for your help guys. Best Regards, Luiz Filipe. -----Mensagem original----- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nome de Joachim Bauch Enviada em: quarta-feira, 2 de maio de 2007 08:54 Para: [email protected] Assunto: [Red5] [Fwd: [Red5devs] Changed to Mina 1.1, and other changes.] To quote Luke: "Can people have a test and see if these changes, a) work for you, b) fix any the freezing or memory issue. Have not tested with Java 6 yet. Let me know if it works ok." -------- Original-Nachricht -------- Betreff: [Red5devs] Changed to Mina 1.1, and other changes. Datum: Wed, 2 May 2007 22:40:58 +0700 Von: Luke Hubbard <[EMAIL PROTECTED]> Antwort an: [EMAIL PROTECTED] An: [EMAIL PROTECTED] Hi All, I did some digging into the memory issue and it does seem like we were leaking some buffers.. The really strange thing is its not our code not releasing them, it seems its a new thing happening with mina 1.0.1 and 1.1. Anyway, I hacked a solution to the problem, flushing after each write and releasing the buffers manually. Only this causes another issue. Mina does release some of the buffers so those already released thow an error. Ok so we could just ignore those exceptions, but it leaves a bad feeling. So.. I decided lets see what AsyncWeb does. I went and had a look at the code, ported the http mina tansport to rtmp mina transport, upgraded to mina 1.1 and changed to heap buffers. Heap buffers dont need to be released.. Oh joy!. The config for the setup of rtmp has changed a little, no more wiring it all together with spring, thats done by the transport bean. IMHO this simplifies the config since we just have a list of properties people can change. I've added these to red5.properties. Internally the tranport uses (#cpu +1) io threads and 16 (is the default) event threads. Event threads can be set from red5.properties. Here is the new red5.properties # HTTP http.host=0.0.0.0 http.port=5080 # RTMP rtmp.host=0.0.0.0 rtmp.port=1935 rtmp.event_threads=16 rtmp.send_buffer_size=271360 rtmp.receive_buffer_size=65536 rtmp.ping_interval=5000 rtmp.max_inactivity=60000 # RTMPT rtmpt.host=0.0.0.0 rtmpt.port=8088 rtmpt.ping_interval=5000 rtmpt.max_inactivity=60000 Can people have a test and see if these changes, a) work for you, b) fix any the freezing or memory issue. Have not tested with Java 6 yet. Let me know if it works ok. - Luke _______________________________________________ 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
-- 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
