We used to get the OOME after every dozen or so redeploys in development. We're using JBoss+Tomcat and it does lose memory after every hot-deploy.
* I looked at the heap with JProfiler. It has a free 10-day-evaluation version, so if you work quickly it's free. I was happy enough with the results that I bought a copy. What a concept. * I found some sloppy references of my own doing. My custom Engine was hanging onto a reference to the Visits, and the Visit was referring to my model-layer object graph. Doh. Beware of static non-final instance variables in the base classes. * There were two postings on this list on January 31st about OOME. MindBridge recommended some extra JVM switches which seemed to help avoid the error after frequent redeploys in development. My complete set of JVM options is this: -server -ea -Dorg.apache.tapestry.disable-caching=true -Xms256m -Xmx256m -XX:MaxNewSize=256m -XX:MaxPermSize=256m I haven't seen an OOME in months. ----- Original Message ----- From: "Ryan Phelan" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, May 30, 2005 11:01 PM Subject: Tapestry and OutOfMemoryError > When the J2EE server is run with the JVM arguments > -Dorg.apache.tapestry.disable-caching=true, does tapestry keep creating > objects and not Garbage collect them? When I have the argument set, I > get OutOfMemoryErrors when developing my code after working with my web > application for about 5 mins. Anyone have OutOfMemoryErrors when using > Tapestry? > Thank you! > > Ryan > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
