Hi, Robert J Morman schrieb: > Good afternoon. We run a portal solution on top of Tomcat 6.0.16 (and > Java 1_5_16). We are running out of PermGen space for several instances > of tomcat, which I believe could be some bad code we've received from > our development team. > > To test a theory, I'd like to expand the size of our PermGen memory > space from the 64m default to 128m (and possibly higher). I know by > increasing this setting, I could just be delaying the inevitable. I am > running Lambda Probe (LP), allowing me to see the various memory > allocations and I see (as well in the logs), PermGen cap out and then > continuous GC occurring. > > I have a 2-part question. > > 1. In Tomcat6w.exe, I set one java_opt to include -XX:MaxPermGen=128m,
MaxPermGen is wrong, MaxPermSize is right. Have fun with http://blogs.sun.com/watt/resource/jvm-options-list.html > but the tomcat service then does not start up. When I change it to be > -DXX:MaxPermGen=128m (like a lot of our other settings , it starts up -D sets system properties (an analogy of environment variables in the platform independant Java world), but there will be no code interested in the system property you used, so it simply won't change anything. > just fine. Yet.. Lambda probe still shows that I only have a 64m cap on > PermGen. Am I setting this properly? (everything I read says yes, but > I'm not getting confirmation via LP). Since -D... doesn't change memory settings, you will still run with 64MB max. Regards, Rainer --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
