Geronimo
  1. Geronimo
  2. GERONIMO-4076

Console runs in unhandled exception when user starts module with unresolved dependencies

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.1, 2.1.4
    • Fix Version/s: 2.2
    • Component/s: console
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      1.) The console/web GUI does not explicitly warn the user when he is about to delete a module which other modules depend upon. [Improvement?]

      (Note: the server does then remove the module properly, and all dependent modules are stopped.)

      2.) When the screen is reloaded, the depending modules are displayed as stopped, but not as "missing dependencies". [Improvement?]

      3.) When the user now attempts to restart one of these modules, the request leads to an unhandled exception. The GUI doesn't show up at all. Instead, an error code 500 is displayed (=> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.processAction). [BUG]

        Activity

        David Jencks made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Jarek Gawor made changes -
        Affects Version/s 2.1.4 [ 12313380 ]
        Fix Version/s 2.1.4 [ 12313380 ]
        Donald Woods made changes -
        Fix Version/s 2.1.3 [ 12313316 ]
        Fix Version/s 2.1.4 [ 12313380 ]
        Joe Bohn made changes -
        Fix Version/s 2.1.2 [ 12313123 ]
        Fix Version/s 2.1.3 [ 12313316 ]
        Joe Bohn made changes -
        Fix Version/s 2.1.2 [ 12313123 ]
        Fix Version/s 2.2 [ 12312965 ]
        Daniel made changes -
        Priority Minor [ 4 ] Major [ 3 ]
        Daniel made changes -
        Description 1.) The console/web GUI does not explicitly warn the user when he is about to delete a module which other modules depend upon. [Improvement?]

        (Note: the server does then remove the module properly, and all dependent modules are stopped.)

        2.) When the screen is reloaded, the depending modules are displayed as stopped, but not as "missing dependencies". [Improvement?]

        3.) When the user now attempts to restart this module, this leads to an unhandled exception. The GUI doesn't show up at all. Instead, an error code 500 is displayed (=> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.processAction). [BUG]
        1.) The console/web GUI does not explicitly warn the user when he is about to delete a module which other modules depend upon. [Improvement?]

        (Note: the server does then remove the module properly, and all dependent modules are stopped.)

        2.) When the screen is reloaded, the depending modules are displayed as stopped, but not as "missing dependencies". [Improvement?]

        3.) When the user now attempts to restart one of these modules, the request leads to an unhandled exception. The GUI doesn't show up at all. Instead, an error code 500 is displayed (=> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.processAction). [BUG]
        Daniel made changes -
        Field Original Value New Value
        Description 1.) The console/web GUI does not explicitly warn the user when he is about to delete a module which other modules depend upon. [Improvement?]

        (Note: the server does then remove the module properly, and all dependent modules are stopped.)

        2.) When the screen is reloaded, the depending modules are displayed as stopped, but not as missing dependencies. [Improvement?]

        3.) When the user now attempts to restart a depending module, this leads to an unhandled exception. The GUI doesn't show up. Instead, an error code 500 is displayed (=> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.processAction). [BUG]
        1.) The console/web GUI does not explicitly warn the user when he is about to delete a module which other modules depend upon. [Improvement?]

        (Note: the server does then remove the module properly, and all dependent modules are stopped.)

        2.) When the screen is reloaded, the depending modules are displayed as stopped, but not as "missing dependencies". [Improvement?]

        3.) When the user now attempts to restart this module, this leads to an unhandled exception. The GUI doesn't show up at all. Instead, an error code 500 is displayed (=> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.processAction). [BUG]
        Daniel created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Daniel
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development