In Tapestry 3.0, pages expire after a few minutes. In Tapestry 4.0, pages do not expire (which may in fact be a bug).
For TSS, I disabled page expiration by disabling the JanitorThread, but I can't quite remember how I did it (!). There was some initialization you could do in the ApplicationServlet. I wish I had time to figure it out (I no longer have access to the TSS source code). On 6/20/05, Eric Williams <[EMAIL PROTECTED]> wrote: > We have a Tapestry application with somewhat complicated pages. They take a > while to load the first time someone uses them. As long as visitors keep > requesting pages from the application, they load quickly. But as soon as the > application is not used for a short while, it reverts back to its original > performance, taking a long time to load. > > I assume this is happening because objects in the page pool are expiring > when the application is inactive, and the requested pages must be rebuilt. > I'd like to avoid this performance penalty. Is there some way of increasing > the lifespan of the page pool? > > Any help is much appreciated. > > Regards, > Eric > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
