Error out of memory java

[barichon]

Looking at my server:

Typing top command:

9092 root 20 0 1348m 1.1g 6448 S 123% 14.0%mem 80:16.94 time java command

looking at the error log:

ERROR server comment 2010-06-09 10:39:39 - - - - - 4075.967 - - - - - - - Zero sized function (client:410178772:WIN 10,0,45,2): type:20 size:0 index:1613:a6f1d0fb7076b3d1e4485de4b017e9d107c70c8 6704d22b77e1a19a3d6eccb4a72afec3ae1bd41c32b0c90de0 c4a78732d00528dad60acd9602c549f8c76c10b39dbb331a4f 08464387e6dd5ccc413cc7755e3a3b0f78b98647c3a015f9da 5e4b73ad824869c5fb35083629bb6001f56422b2d375560bcb 87f81030000000001
- - - - - - - - - - - - - - - - - - -
java.lang.OutOfMemoryError: GC overhead limit exceeded


typing a free command:

twain-140:/var/log/wowza# free
total used free shared buffers cached
Mem: 8312444 1835164 6477280 0 34556 599472
-/+ buffers/cache: 1201136 7111308
Swap: 2104504 0 2104504

We are about 700 connected on it.
What would you advice ?

add memory (8 giga are installed...) ? -ulilmit is 20000..., _EXECJAVA=java
JAVA_OPTS was "-Xmx2G", then 1G and now 768M... java is still crashing...

thx by advance,

[Guille]

What version of Java do you have installed?

[barichon]

On my balanced Wowza server:

twain-140:~# java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)


twain-176:~# java -version
java version "1.6.0_06"
Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
Java HotSpot(TM) Server VM (build 10.0-b22, mixed mode)


twain-127:~# java -version
java version "1.6.0_12"
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) Server VM (build 11.2-b01, mixed mode)

[barichon]

an update on this please ?

600 customers on each servers requesting the same thing (approximatively) and no way to fix java crash....

[rrlanham]

Do you have java_opts -server flag ?

Is there a GC line ? Try commenting that out.

It doesn't look like you are running a 64bit system. If true, then you are limited to -Xmx1800M

I wouldn't bring -Xmx down to solve the problem.

Richard

[barichon]

We are running debian lenny x32,

Here is my setenv.sh:

#!/bin/sh

_EXECJAVA=java
JAVA_OPTS="-Xmx1300M -XX:-UseGCOverheadLimit"

# Uncomment to run server environment (faster), Note: will only work if server VM install, comes with JDL
JAVA_OPTS="$JAVA_OPTS -server"

# Better garbage collection setting to avoid long pauses
JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:NewSize=1024m"

# Uncomment to fix multicast crosstalk problem when streams share multicast port
JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"

WMSAPP_HOME=/usr/local/WowzaMediaServer
WMSCONFIG_HOME=/usr/local/WowzaMediaServer
WMSCONFIG_URL=

export WMSAPP_HOME WMSCONFIG_HOME JAVA_OPTS _EXECJAVA

[rrlanham]

Following the General Tuning Guide, you are advised to set Java_Heap to 1500M (or max 1800m) for 32 bit system. So 2G was not a good idea. Also, the guide advices not enabling the GC line by default. Garbage collection is built-in.

Were you having the "multicast crosstalk problem"? That line was uncommented.

Try it like this:

#!/bin/sh

_EXECJAVA=java
JAVA_OPTS="-Xmx1500M"

# Uncomment to run server environment (faster), Note: will only work if server VM install, comes with JDL
JAVA_OPTS="$JAVA_OPTS -server"

# Better garbage collection setting to avoid long pauses
#JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:NewSize=1024m"

# Uncomment to fix multicast crosstalk problem when streams share multicast port
# JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"

WMSAPP_HOME=/usr/local/WowzaMediaServer
WMSCONFIG_HOME=/usr/local/WowzaMediaServer
WMSCONFIG_URL=

export WMSAPP_HOME WMSCONFIG_HOME JAVA_OPTS _EXECJAVA

If you were having the "multicast crosstalk problem", you can uncomment that line.

Richard

[barichon]

ok for 2G, but I also tried other lower value and still the same...
Ok, I'am gonna comment GC. But I uncommented it just because it was crashing...it was a test.

Regards,

[rrlanham]

I also took out "-XX:-UseGCOverheadLimit' since you were having "java.lang.OutOfMemoryError: GC overhead limit exceeded".

Richard

[barichon]

What you have to understand is that file has been patched (tunned) multiple times because the default one was initialy the "cause" of the problem. (If that probleme can be solved).