Hi
after running Apache Tomcat for a whole month without problems, it crashes now too often (after approx. 2 days). The error I get: “java.lang.OutOfMemoryError: requested 140 bytes for CHeapObj-new. Out of swap space?”
My JVM options:
export MALLOC_CHECK_=0
JAVA_OPTS=“-Djava.awt.headless=true”
JAVA_OPTS=“$JAVA_OPTS -server "
JAVA_OPTS=”$JAVA_OPTS -XX:SoftRefLRUPolicyMSPerMB=36000 "
JAVA_OPTS=“$JAVA_OPTS -Xms128m -Xmx768m "
JAVA_OPTS=”$JAVA_OPTS -XX:PermSize=128m "
JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=256m "
Is there a way to find out which process makes Tomcat crashing? (I have two other servlets running in Tomcat) And how to avoid crashing Tomcat this often? [GeoServer 1.6.4b, Apache Tomcat 5.5.25 on a Red Hat Enterprise Linux ES release 4 (Nahant Update 6)]
regards
Stefan
Mit freundlichem Gruss
Stefan Ziegler
Leiter Aufsicht
Kanton Solothurn
Bau- und Justizdepartement
Amt für Geoinformation
Rötistrasse 4
4501 Solothurn
Telefon 032 627 75 96
Telefax 032 627 75 98
stefan.ziegler@anonymised.com
http://www.so.ch
I don't have a clear answer, but you may be able to peak into the process by running visualvm: https://visualvm.dev.java.net/
We have several GeoServer instances that have been up for extended periods of time, so I'd be surprised if there are major memory leaks in the WMS / Shapefile / Postgis context.
Other relevant questions
1) What version of Java are you running?
2) How much physical memory does the machine actually have? Try setting both Xms and Xmx to 512
3) Alternatively, move GeoServer to it's own application server (can be on the same machine), see what eats memory.
-Arne
Ziegler Stefan wrote:
Hi
after running Apache Tomcat for a whole month without problems, it crashes now too often (after approx. 2 days). The error I get: "java.lang.OutOfMemoryError: requested 140 bytes for CHeapObj-new. Out of swap space?"
My JVM options:
export MALLOC_CHECK_=0
JAVA_OPTS="-Djava.awt.headless=true"
JAVA_OPTS="$JAVA_OPTS -server "
JAVA_OPTS="$JAVA_OPTS -XX:SoftRefLRUPolicyMSPerMB=36000 "
JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx768m "
JAVA_OPTS="$JAVA_OPTS -XX:PermSize=128m "
JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=256m "
Is there a way to find out which process makes Tomcat crashing? (I have two other servlets running in Tomcat) And how to avoid crashing Tomcat this often? [GeoServer 1.6.4b, Apache Tomcat 5.5.25 on a Red Hat Enterprise Linux ES release 4 (Nahant Update 6)]
regards
Stefan
Mit freundlichem Gruss
Stefan Ziegler
Leiter Aufsicht
Kanton Solothurn
Bau- und Justizdepartement
Amt für Geoinformation
Rötistrasse 4
4501 Solothurn
Telefon 032 627 75 96
Telefax 032 627 75 98
stefan.ziegler@anonymised.com
http://www.so.ch
------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hi Stefan,
I found this:
The next improvement is visible when the system is almost out of swap space and an allocation from the native heap fails in the VM. In that case the VM aborts and you get a one-line error such as the following:
Exception java.lang.OutOfMemoryError: requested 16 bytes for CHeapObj-new. Out of swap space?
This message has been known to confuse a lot of developers. At first glance it might it might look like that the java heap is full. Of course if you increase the size of the heap with the -mx option it might make the problem worse as the larger java heap means there is less native memory available.
from: http://blogs.sun.com/alanb/entry/outofmemoryerror_looks_a_bit_better
I don't know whether it will help but maybe you can give it a try. Could there really be problems with the swap space? You'd better check it.
- mika -
Ziegler Stefan kirjoitti:
Hi
after running Apache Tomcat for a whole month without problems, it crashes now too often (after approx. 2 days). The error I get: "java.lang.OutOfMemoryError: requested 140 bytes for CHeapObj-new. Out of swap space?"
My JVM options:
export MALLOC_CHECK_=0
JAVA_OPTS="-Djava.awt.headless=true"
JAVA_OPTS="$JAVA_OPTS -server "
JAVA_OPTS="$JAVA_OPTS -XX:SoftRefLRUPolicyMSPerMB=36000 "
JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx768m "
JAVA_OPTS="$JAVA_OPTS -XX:PermSize=128m "
JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=256m "
Is there a way to find out which process makes Tomcat crashing? (I have two other servlets running in Tomcat) And how to avoid crashing Tomcat this often? [GeoServer 1.6.4b, Apache Tomcat 5.5.25 on a Red Hat Enterprise Linux ES release 4 (Nahant Update 6)]
regards
Stefan
Mit freundlichem Gruss
Stefan Ziegler
Leiter Aufsicht
Kanton Solothurn
Bau- und Justizdepartement
Amt für Geoinformation
Rötistrasse 4
4501 Solothurn
Telefon 032 627 75 96
Telefax 032 627 75 98
stefan.ziegler@anonymised.com
http://www.so.ch
------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users