[jira] Updated: (GERONIMO-4794) Difference in application start/stop and restart behavior

["Ashish Jain (JIRA)" <ji...@apache.org>]

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

Ashish Jain updated GERONIMO-4794:
----------------------------------

    Fix Version/s:     (was: 2.1.5)
                   Wish List

> Difference in application start/stop and restart behavior
> ---------------------------------------------------------
>
>                 Key: GERONIMO-4794
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4794
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 2.1.3, 2.1.4
>         Environment: Windows XP, G 214
>            Reporter: Ashish Jain
>            Assignee: Ashish Jain
>             Fix For: Wish List
>
>         Attachments: DummyProject.war
>
>
> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.