Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-6199

JBoss allows duplicate user and local dependencies

    XMLWordPrintable

Details

    Description

      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

      Attachments

        Issue Links

          is cloned by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-24443 [GSS](7.4.z) WFCORE-6199 - JBoss allows duplicate user and local dependencies

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFCORE-6188 Eliminate useless locking in ServiceModuleLoader

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODULES-435 Module.addExportedPaths performance degraded by ModuleIdentifier deprecation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Pull Request Sent

          Activity

            People

              ropalka Richard Opalka
              rhn-support-aogburn Aaron Ogburn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: