While doing some load testing with WFS-T (inserting information) I ran into java.lang.OutOfMemoryError (Java heap space). I reran the test several times, each time watching the amount of available memory in Tomcat. GeoServer would work fine but the amount of available memory would steadily decrease until it about 3 mb (from 500 mb) and then run out of heap space.
The load testing is 90 to 100 insertions a second for about 5 minutes solid. The stack trace I saw while trying to shutdown Tomcat (after the heap space error) mentioned a thread named "WeakCollectionCleaner". Is there a hashtable that is "caching" the feature type data? If there is such a cache, is there a way to configure a cap on the size of the hashtable or a frequency for cleaning the hashtable? The stack trace: Dec 21, 2010 2:24:00 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [/geoserver] registered the JBDC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Dec 21, 2010 2:24:00 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [/geoserver] registered the JBDC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Dec 21, 2010 2:24:00 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [/geoserver] registered the JBDC driver [org.hsqldb.jdbcDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Dec 21, 2010 2:24:00 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/geoserver] appears to have started a thread named [WeakCollectionCleaner] but has failed to stop it. This is very likely to create a memory leak. Dec 21, 2010 2:24:00 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/geoserver] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. Dec 21, 2010 2:24:00 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/geoserver] appears to have started a thread named [WeakCollectionCleaner] but has failed to stop it. This is very likely to create a memory leak. Environment: GeoServer 2.1 Beta 3 PostgreSQL 9.0.1 PostGIS 1.5 Tomcat 6.0.29 Windows Vista Thanks in advance, Leon ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
