On Thursday, December 22, 2011 1:18 AM, Andrea Aime < [email protected] > wrote: > > On Thu, Dec 22, 2011 at 1:01 AM, Jeff Dege <[email protected]> wrote: > > > > We're running GeoServer 2.1.0 on TomCat6 on an Ubunto 10.04 box, with a > > fairly modest load (just a few dozen > users), and we're having repeated problems with Java out-of-memory errors. > > > > [...] > > > > Any ideas?
> Over time we fixed a few memory leaks related to WFS usage, you might want to > upgrade to 2.1.3. We have customers working against the current 2.1.0 system, so we can't just shut it down. We'd need to bring up the new system in parallel, and move the data over. Can you point me to any information on how to do that? > A way to investigate what is leaking is to wait for your server to get close > to the OOM and then use > something like this on the command line (assuming the JDK is in your path): > > jmap -histo:live <jvmProcessId> > > It will dump a histogram with the classes that use the most memory. See also: > http://docs.geoserver.org/latest/en/user/production/troubleshooting.html#jmap I'll look into finding a jmap for the Sun jdk. ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
