portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Created: (JS2-341) Add State to Jetspeed Engine for Error Conditions
Date Fri, 19 Aug 2005 16:17:59 GMT
Add State to Jetspeed Engine for Error Conditions

         Key: JS2-341
         URL: http://issues.apache.org/jira/browse/JS2-341
     Project: Jetspeed 2
        Type: New Feature
  Components: Components Core  
    Versions: 2.0-M4, 2.0-FINAL    
    Reporter: David Sean Taylor
 Assigned to: David Sean Taylor 
     Fix For: 2.0-M4

This feature addresses a 'user experience' problem: displaying stack traces to the end user.
For example, If I change my database connection to a bad setting, and then try to hit the
portal, I get this in my browser:

javax.servlet.ServletException: Failed to initalize jetspeed. org.apache.jetspeed.exception.JetspeedException:
Unable to create Engine


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


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.

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message