-
Enhancement
-
Resolution: Done
-
Major
-
None
JBoss can allow multiple duplicate user or local dependencies. This could occur if jars are being loaded through MANIFEST.MF class-path entries and I saw this do things like exasperate issues from WFCORE-6188 and MODULES-435 for a slower start up. The attached app demonstrates that slowness and takes over 90 seconds to start:
17:57:20,493 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 28.0.0.Beta1-SNAPSHOT (WildFly Core 20.0.0.Beta4) started in 97812ms - Started 1019 of 1268 services (568 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml
If you capture a heap dump deploying that test app, run an OQL like the following and you can see the deployment modules with an inordinate number of dependencies and these are from many duplicate entries:
SELECT module.name.toString(), allDependencies.size, localDependencies.list.size FROM org.jboss.as.server.moduleservice.ModuleLoadService
- is cloned by
-
JBEAP-24443 [GSS](7.4.z) WFCORE-6199 - JBoss allows duplicate user and local dependencies
- Closed
- relates to
-
MODULES-435 Module.addExportedPaths performance degraded by ModuleIdentifier deprecation
- Closed
-
WFCORE-6188 Eliminate useless locking in ServiceModuleLoader
- Closed