> I see, that is very helpful to me to see that someone else has > the error too. Did you guys ever find out what the actual cause is? Like > you, I'm suspecting that it has something to do with tapestry debug mode > (caching.disabled=true), because it works *endless* as you said when set > to "false", and errors out when set to "true". Would be good to know :)
A good profiler would help you to find your "big" objects, as well as the GC roots for these objects (ie, what's holding them alive). Have you tried running your application through a profiler like, let's say, YJP? -- Marcus Brito --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
