Are you leaving expensive reference chains attached to the tapestry
page objects? Remember that with caching on the pages go into a pool so if
you allocate a massive object tree during page render and don't null it out
during initialize, it'll sit there in memory forever (or until the page
comes back out of pool and the reference gets set to something else).
--- Pat
> -----Original Message-----
> From: Ryan Phelan [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 30, 2005 8:15 PM
> To: 'Tapestry users'
> Subject: RE: Tapestry and OutOfMemoryError
>
> Thanks for the quick Response!, Yes I'm well aware of the gc capabilites
> of Java. (It was a nice refresher though :)... Anyway, while hunting for
> such *leaks*, I need to target (or eliminate) Tapestry as the cause of
> my OutOfMemoryErrors. Seems to work fine when disable-caching is set to
> false, but when it is true, then I get OutOfMemoryErrors. Anyone else
> run into this problem? Is it a common and known thing in the tapestry
> world? Does Tapestry expect you to make a few changes, shutdown the
> server, and then go at it again, when writing/debugging a web
> application based on tapestry (when disable-caching = true, that is) ?
>
> Thanks again! :)
>
> -----Original Message-----
> From: Patrick Casey [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 30, 2005 10:09 PM
> To: 'Tapestry users'
> Subject: RE: Tapestry and OutOfMemoryError
>
>
>
> Tapestry doesn't have control of when things get garbage
> collected; that's up the the JVM (unless you manually call system.gc()
> and even then you're only *suggesting* that the JVM do a round of
> garbage collection). If you're running out of memory, I'd seriously look
> at your own object creation patterns and/or caching code.
>
> Remember that things won't be collected unless they're
> unreachable so if there exists a legal reference chain to an object,
> nomatter how tenuous, it's not going anywhere. You *can* leak memory in
> java if you A) overcache or B) leave lots of obsolete reference chains
> intact.
>
> -- pat
>
> > -----Original Message-----
> > From: Ryan Phelan [mailto:[EMAIL PROTECTED]
> > Sent: Monday, May 30, 2005 8:02 PM
> > To: [email protected]
> > 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]
>
>
>
>
> ---------------------------------------------------------------------
> 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]
