[GERONIMO-4794] Difference in application start/stop and restart behavior

• Type: Bug
• Status: Open
• Priority: 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)

Environment

Windows XP, G 214

• Assignee: Ashish Jain
• Reporter: Ashish Jain
• Created: 14/Aug/09 08:29
• Updated: 15/Mar/10 08:02

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