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]
