Hi Derek,
Thanks for taking the time to investigate this.
Please know that the IPT uses Google Guice which has a known memory leak [ e.g. 1], but is not particularly critical, and we are all waiting for some time for it to be fixed in the next major release. You might find that this is the cause of the error report. There have been IPTs known to run for more than a year without issues, so I hope you don't find this to be critical to your deployment - if you find you are doing a lot of redeployments however, then perhaps it would become more problematic.
HTH, Tim
[1] http://code.google.com/p/google-guice/issues/detail?id=288
On Sep 5, 2012, at 5:02 PM, Derek Broughton wrote:
I'm running IPT in Tomcat and experiencing PermGen memory errors.
From the Tomcat Manager, I can use "Find Leaks", and as suspected get:
"The following web applications were stopped (reloaded, undeployed), but their classes from previous runs are still loaded in memory, thus causing a memory leak (use a profiler to confirm): /ipt"
http://frankkieviet.blogspot.ca/2006/10/classloader-leaks-dreaded-permgen-sp... does a pretty good job of explaining _why_ this happens. Unfortunately, I can't seem to find part two which is supposed to tell me how to go about fixing it. His blog also only deals with memory leaks on redeployment, but this is happening any time IPT is running for a while, so IPT is leaking in ordinary use, rather than just at context initialization.
I'm going to try to find what's happening with a profiler, but I'm new to this...
Tomcat Version 6.0.35 JVM Version Sun 1.6.0_24-b07 Linux 2.6.24-28-generic amd64 -- derek _______________________________________________ IPT mailing list IPT@lists.gbif.org http://lists.gbif.org/mailman/listinfo/ipt