[jboss-jira] [JBoss JIRA] (AS7-5995) After deploy an application with a wrong module slot dependency the module loader does not recover
Chao Wang (JIRA)
jira-events at lists.jboss.org
Fri Nov 30 03:03:21 EST 2012
[ https://issues.jboss.org/browse/AS7-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738399#comment-12738399 ]
Chao Wang commented on AS7-5995:
--------------------------------
module service failed to start because of dependency problems, as a result the module(same ModuleIdentifier) is never unloaded and stuck with wrong slot, we probably need to unload in undeploy() of ModuleSpecProcessor
> After deploy an application with a wrong module slot dependency the module loader does not recover
> --------------------------------------------------------------------------------------------------
>
> Key: AS7-5995
> URL: https://issues.jboss.org/browse/AS7-5995
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.2.0.Alpha1
> Environment: Tested with 7.2. upstream
> commit ed2bc551a55ec6a8167a8657cbb5d8abc6e07748
> Date: Thu Nov 15 10:15:22 2012 +0100
> standalone mode, no difference whether CLI or file-system scanner
> Reporter: Wolf-Dieter Fink
> Assignee: Chao Wang
> Labels: dependency, modules
> Attachments: server.log, server.log
>
>
> If an application is deployed with a dependency and specify a slot in jboss-deployment-structure.xml:
> <module name="wfink.tools.performance" slot="1.0" export="true"/>
> the module loader will not correct load a new deployment after failing with 'JBAS018759' Caused by: org.jboss.modules.ModuleNotFoundException: Module wfink.tools.performance:1.1 is not found in local module loader.
> If after such message the application.ear contain a correct slot, or even no slot entry, the module loader fail with the message above. The slot number is the same as of the failed deployment.
> If the server is restarted the application deploy succeeds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list