If you're using Tomcat and have access to the startup scripts, I'd suggest turning on JMX so that you can have a look inside the memory heaps using jconsole.
To do this add a line to tomcat/bin/startup.sh just before the exec at the end: export CATALINA_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9098 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false" (Note that this assumes an internal dev box, as there's no ssl or authentication turned on.) You can then connect to it with jconsole (in your java install's bin directory). The next step would be some more automated profiling, but just visually looking at the state of the heaps during a load test can be quite helpful. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 22 February 2007 13:22 > To: users@tapestry.apache.org > Subject: RE: OutOfMemoryError after serving N pages > > Yeah, that is more sinister. > > Try dropping a lambdaprobe.war in your container and watching > what happens to your app as you serve up N pages. > > It isn't as detailed as JProbe or anything like that, but > you'll be up and running in 5 minutes and it may give you a > better overview of your runtime environment and any resource > constraints you may unknowingly have. > > http://www.lambdaprobe.org/d/index.htm > > > Tom > > -----Original Message----- > From: Arjan Verstoep [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 22, 2007 8:15 AM > To: Tapestry users > Subject: Re: OutOfMemoryError after serving N pages > > [EMAIL PROTECTED] wrote: > > We had the same thing, and in our case it was related to a small > PermGen > > Space setting in our Tomcat container. > > > > My understanding of the Sun JVM is that it partitions up > its allocated > > memory into heap, perm gen, etc. chunks and that the Perm > Gen space is > > where all "meta data" about classes gets stored. In "modern" JEE > > programming with all the CGLIB and just-in-time abstract class > overrides > > & instantiation, the Perm Gen space tends to blow up quicker. > > > > Anyway, try throwing a -XX:MaxPermSize=256m on your JVM startup and > see > > if that helps. > > > > Note: if you're actually running out of PermGen space, you'll see a > > reference to that in your OOME. If you are just getting plain old > > OOMEs, it sounds like something more sinister. > > > > HTH, > > Tom > > > > > My JVM is complaining about heap space, so I fear that it is > something sinister... > > 10:36:23,289 ERROR [MusiController4]:253 - > Servlet.service() for servlet MusiController4 threw exception > java.lang.OutOfMemoryError: Java heap space > > > ~Arjan Verstoep > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
