]
Erich Duda updated WFCORE-3895:
-------------------------------
Component/s: Embedded
(was: Modules)
module.path cannot be modified after it is set
----------------------------------------------
Key: WFCORE-3895
URL:
https://issues.jboss.org/browse/WFCORE-3895
Project: WildFly Core
Issue Type: Bug
Components: Embedded
Affects Versions: 5.0.0.Beta5
Reporter: Erich Duda
Assignee: David Lloyd
Priority: Blocker
*Scenario:*
* Run CLI in non-modular class loading mode.
* Run embed-server with {{--jboss-home}} pointing to server A
* Stop embed-server
* Remove server A
* Run embed-server with {{--jboss-home}} pointing to server B
*Expectation:* embed-server with {{--jboss-home}} pointing to server B will boot.
*Reality*: The following error message is thrown. As you can see the embed server tries
to load modules from server A directory even if the jboss-home was set to server B.
{code}
Cannot start embedded server: The first directory of the specified module path
/home/eduda/Projects/wildfly/dist/target/wildfly-A/modules is invalid or does not exist.
{code}
*Users impact:* Behavior of non-modular class loading \[1\] has changed. This change can
break user's automation or tests.
*Blocker priority* was chosen because this is change in behavior against Wildfly 12.
*Technical details*
When the embed-server is started for the second time, following warning is logged.
{code}
2018-05-28 08:10:57,621 WARN [org.jboss.as.embedded] (main) WFLYEMB0145: The module
loader has already been configured. Changing the module.path property will have no effect
{code}
It seems that the change in behavior was caused by commit \[2\].
\[1\]
http://wildfly.org/news/2015/03/13/Offline-CLI/#classloading
\[2\]
https://github.com/wildfly/wildfly-core/commit/22f3956f1adcdf8b1cb11e24f2...