Thank you for your answer, The RED 5 server is started by a script in init.d and JAVA_OPT are almost the same as in red5-hiperf.sh.
JAVA_OPTS="-Xrs -Xms512M -Xmx3072M -Xss128K -XX:NewSize=256m -XX:+UseLargePages -XX:SurvivorRatio=16 -XX:MinHeapFreeRatio=20 -XX:+AggressiveHeap -XX:+ExplicitGCInvokesConcurrent -XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true - Xverify:none" The real problem are Share Screen, because all problems starts when share screen is activated. I will make more tests with more RAM. Thank you again, Geo P.S. why co-browsing doesn't exist in this version? On 1 feb., 15:15, "[email protected]" <[email protected]> wrote: > Yeah, > > this is definitly a High Load issue. > But is it really the complete log? > > There might be improvements by upgrading to newer Red5 version, but you have > to do it carefully as long as there is no final release of the current > version. > > The exceptions in the Play Engine could lead to the problems but there is > actually no Heap-Space error or similar. > > You could also try to configure the JAVA settings in the red5-highperf.sh. > Did you use that script to start the server and to tweak the settings > already? > > Maybe you should give your server more RAM by default. > > Sebastian > -- You received this message because you are subscribed to the Google Groups "OpenMeetings User" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
