[jboss-jira] [JBoss JIRA] (WFLY-4828) Server starts when new module contains wrong dependency
[
https://issues.jboss.org/browse/WFLY-4828?page=com.atlassian.jira.plugin....
]
Hayk Hovsepyan commented on WFLY-4828:
--------------------------------------
Steps our test framework uses to reproduce: (can be executed manually).
1. Extract attached "remote-messaging.zip" file in WFLY
modules/system/layers/base/org/jboss/ directory.
2. Deploy attached "crashrecovery-jms.jar" file into WFLY
standalone/deployments.
3. Start the server in standalone mode.
4. Connect to server via CLI.
5. Execute CLI command
"/subsystem=naming/binding="java:/XAQCF":add(module="org.jboss.remote-messaging",binding-type="object-factory",class=org.jboss.qa.IBMMQObjectFactory)".
You will see the failure description: "WFLYNAM0052: Could not load module
org.jboss.remote-messaging:main". This is default message when requested module does
not exist.
In module.xml file of attached "remote-messaging" module there is a wrong
dependency "<module name="org.jboss.wrongmodule"/>", if you
remove this line and restart the server, CLI command works fine.
Server starts when new module contains wrong dependency
-------------------------------------------------------
Key: WFLY-4828
URL: https://issues.jboss.org/browse/WFLY-4828
Project: WildFly
Issue Type: Bug
Components: Server
Reporter: Hayk Hovsepyan
Assignee: Jason Greene
Attachments: crashrecovery-jms.jar, remote-messaging.zip
When there is dependency to non existing modules in a new added module configuration
file, server starts without any problem. But should fail.
The same non existent dependency added into existing modules configurations, causes
server to not start and appropriate errors are shown.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)