Geronimo
  1. Geronimo
  2. GERONIMO-4794

Difference in application start/stop and restart behavior

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.1.3, 2.1.4
    • Fix Version/s: Wish List
    • Component/s: console
    • Security Level: public (Regular issues)
    • Labels:
      None
    • Environment:

      Windows XP, G 214

      Description

      There is a difference in behavior of start/stop and restart of application. Currently start/stop functions in the following manner once you issue the stop command configurations will be stopped, than unloaded. This will also destroy the current classloader. Once a start is issued the configurations will loaded and than started. This will also result in the creation of new classloaders.

      In case of restart same modules will be started as before the restart command, and same old classloaders will be used. This results in loss of functionality in which some of the static variables are not re-initialized and can no longer be useful.

      So as to fix this issue up, restart code needs to be modified so that new classloaders are created.

      For more information please refer the following discussion
      http://www.nabble.com/Difference-in-start-stop-and-restart-behavior-td24933496s134.html

        Activity

        Ashish Jain created issue -
        Hide
        Ashish Jain added a comment -

        a Sample to recreate this issue

        Show
        Ashish Jain added a comment - a Sample to recreate this issue
        Ashish Jain made changes -
        Field Original Value New Value
        Attachment DummyProject.war [ 12416540 ]
        Hide
        Ivan added a comment -

        There is a related JIRA, GERONIMO-4369
        I think we could do the related work of the restart action in the portlet, I mean stop->unload->load->start, and keep a record of those modules that need to be start later.

        Show
        Ivan added a comment - There is a related JIRA, GERONIMO-4369 I think we could do the related work of the restart action in the portlet, I mean stop->unload->load->start, and keep a record of those modules that need to be start later.
        Hide
        David Jencks added a comment -

        I find it extremely implausible that the classloader for a dependent plugin would not be recreated when the plugin is stopped and started – it gets a new ancestor.

        In any case, we aren't fixing this for 2.2

        Show
        David Jencks added a comment - I find it extremely implausible that the classloader for a dependent plugin would not be recreated when the plugin is stopped and started – it gets a new ancestor. In any case, we aren't fixing this for 2.2
        David Jencks made changes -
        Fix Version/s Wish List [ 12310202 ]
        Fix Version/s 2.2 [ 12312965 ]
        Ashish Jain made changes -
        Fix Version/s 2.1.5 [ 12313729 ]
        Fix Version/s Wish List [ 12310202 ]
        Ashish Jain made changes -
        Fix Version/s Wish List [ 12310202 ]
        Fix Version/s 2.1.5 [ 12313729 ]

          People

          • Assignee:
            Ashish Jain
            Reporter:
            Ashish Jain
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development