I'm guessing you're using T4 with caching disabled? This is a known "issue" and there's not much you can do about it other than periodically restart Tomcat. The issue is related to cache being disabled, so you won't run into it in production.
-- Kevin On 2/4/08 12:39 AM, in article [EMAIL PROTECTED], "learner" <[EMAIL PROTECTED]> wrote: > i very frequent get this error after using tomcat for sometime. i know > increasing memory will temporary delay the problem. but is anyone of you > experience this when using tapestry? > coz i get it too frequent and very curious... > > > --------------------------------------------------------------------- > 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]
