Hi, This is my first post. Don't know if this should have been posted in the user forum.
We are struggling with a major memory leak. Our platform: o Geoserver 2.0.2, 821 layers, 151 workspaces/datastores o Win2003 32-bit 4 GB, Java 1.6.0_21, Tomcat 6.0.26, JVM minmx=memmx=1420 MB We are only using WMS and WFS. The JVM runs out of heap space very fast, forcing us to reboot Tomcat every 2 hours. VisualVM reports that the top consumers (933 MB in total) are: java.lang.String: 251 MB char[]: 235 MB org.apache.xerces.dom.AttrNSImpl: 217 MB java.util.HashMap$Entry 92 MB org.apache.xerces.dom.TextImpl: 70 MB org.eclipse.xsd.impl.XSDElementDeclarationImpl: 68 MB The AttrNSImpl looks suspicious. Geoserver 2.0.2 uses Xerces 2.6.2. The current version is Xerces 2.10.0 (released June 19 2010). Presumably, it contains a fix for an AttrNSImpl related leak (see http://web.archiveorange.com/archive/v/4o5nETE1HwzVF6W9n09z), amongst many other fixes (including memory leaks). However, the above numbers were generated with geoserver 2.0.2 using xerces 2.10.0 (we bluntly replaced the Xerces jar). Is anyone familiar with this behavior? Is Xerces the culprit or are other objects unintentionally holding references to Xerces objects? Is this related to http://jira.codehaus.org/browse/GEOS-3534 ?? We also tried the nightly 2.0.x build from July 12 2010. Unfortunately, the heapspace gets exhausted in a similar way. Any help appreciated. Greetings, Egon ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
