Hi, on Linux or other Unix-like system, one possibility is that Jetty unpacked your WAR to /tmp and tmpwatch or something similar removed some not recently used files.
Cezary On Mon, Mar 21, 2011 at 4:21 PM, Rich M <rich...@moremagic.com> wrote: > Hi, > > I've been running a production version of a tapestry application for a > couple months now. Just the other day it was reported to me that the > application was no longer resolving pages normally, but instead displaying a > directory view from the root context. > > Restarting the application solved the problem, but I'm at a loss as to the > cause. Looking through the application logs, the only unusual logging I > noticed was that sometime during the timeframe in which the problem was > expected to occur, the TapestryModule.ComponentClassResolver fired off 3 > lines of logging similar to when you execute the start-up of a Tapestry > application. > > Namely, it displayed lists of available pages, available components, and > available mixins. The list of available pages was significantly reduced from > the actual pages within the application. It seemed like an at-random > mini-subset of the actual pages in the application. There is nothing to > indicate someone had tried to start/restart the application again or > anything along those lines. > > Considering the minimal amount of information I have at hand, I was curious > to know if this ComponentClassResolver issue might look familiar to anyone? > Or perhaps at least an idea of what might cause the ComponentClassResolver > to behave as it had so I can follow up with a code review of my application? > I run the application in a standalone Jetty 6.1.26 as a WAR deployment. > > Thanks, > Rich > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
