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] [Resolved] (JS2-341) Add State to Jetspeed Engine for Error Conditions
Date Wed, 04 May 2011 04:38:03 GMT

     [ https://issues.apache.org/jira/browse/JS2-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

David Sean Taylor resolved JS2-341.

    Resolution: Not A Problem

Looks like Ate added similar support with the Jetspeed Diagnostics page, to better provide
stack traces and program state. I am going to close this as no longer a problem

> Add State to Jetspeed Engine for Error Conditions
> -------------------------------------------------
>                 Key: JS2-341
>                 URL: https://issues.apache.org/jira/browse/JS2-341
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Components Core
>    Affects Versions: 2.2.0
>            Reporter: David Sean Taylor
>            Assignee: David Sean Taylor
>             Fix For: 2.2.2
> 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
>     org.apache.jetspeed.engine.JetspeedServlet.doGet(JetspeedServlet.java:206)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> Ugly.
> 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.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

View raw message