-
Bug
-
Resolution: Done
-
Critical
-
EAP 6.1.0.Alpha (7.2.0.Final)
ServiceModuleLoader can't properly unload module if it failed to load module due to wrong dependency.
The codes below take care of unload operation.
org.jboss.as.server.moduleservice.ServiceModuleLoader.java
case STOP_REQUESTED_to_STOPPING: { log.tracef("serviceStopping: %s", controller); ModuleSpec moduleSpec = this.moduleSpec; try { *Module module = loadModule(moduleSpec.getModuleIdentifier());* *unloadModuleLocal(module);* } catch (ModuleLoadException e) { // ignore, the module should always be already loaded by this point, // and if not we will only mask the true problem } // TODO: what if the service is restarted? controller.removeListener(this); break; }
The line unloadModuleLocal(module) can not be reached because the previous loadModule(moduleSpec.getModuleIdentifier() will throw ModuleLoadException if module has dependency problem.
- relates to
-
AS7-5995 After deploy an application with a wrong module slot dependency the module loader does not recover
- Resolved
-
MODULES-149 Installing a broken dependency leaves ModuleLoader in broken state
- Resolved