> > I propose that the Jetspeed engine always completes initialization, even > on error conditions. The engine will have 'state' attribute to > determine if the engine is running or in > > engine.getState() > > returning states such as RUNNING, INITIALIZING, DOWN, ERROR > > Then a valve can check the engine state, and redirect to servlet pages > based on the state, or pass thru on the RUNNING state.
+1! This is a great idea. > > This leads to an interesting challenge: what if the database comes up? > Should we just restart the app server? > Thats certainly the easiest solution. > A retry thread would be another solution I think just re-creating a brand new Engine instance and starting it in the JetspeedServlet would work just as well as long as the app server can recover cleanly (if we are using the app servers datasource). Otherwise, a container restart would be required. > > Well, I didn't mean to hijack your thread and sorry if I got off topic. > I hope we are trying to solve the same problem. > > Im going to create a JIRA issue to further explore the engine state > feature > > > > > --------------------------------------------------------------------- > 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]
