Jetspeed 2
  1. Jetspeed 2
  2. JS2-341

Add State to Jetspeed Engine for Error Conditions

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Not a Problem
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.2
    • Component/s: Components Core
    • Labels:
      None

      Description

      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

        Activity

        Hide
        David Sean Taylor added a comment -

        This one wont make it into 2.0 release

        Show
        David Sean Taylor added a comment - This one wont make it into 2.0 release
        Hide
        David Sean Taylor added a comment -

        well, this one is getting deferred to 2.2 (sigh)

        Show
        David Sean Taylor added a comment - well, this one is getting deferred to 2.2 (sigh)
        Hide
        Ate Douma added a comment -

        We don't have the time left to include it 2.2 either. Deferring to 2.3

        Show
        Ate Douma added a comment - We don't have the time left to include it 2.2 either. Deferring to 2.3
        Hide
        David Sean Taylor added a comment -

        make that 2.2.2

        Show
        David Sean Taylor added a comment - make that 2.2.2
        Hide
        David Sean Taylor added a comment -

        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

        Show
        David Sean Taylor added a comment - 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

          People

          • Assignee:
            David Sean Taylor
            Reporter:
            David Sean Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development