Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9954

Too many services and dependencies created for EJBs

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 17.0.0.Alpha1, 17.0.0.Final
    • None
    • EJB
    • None
    • Medium

    Description

      If a deployment contains more than 2730 EJBs, the deployment's INSTALL phase will get a stack trace like this:

      2018-03-25 08:22:34,115 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."example.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."example.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "example.jar"
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: Too many dependencies specified (max is 16383)    .......... (*1)
        at org.jboss.msc.service.ServiceBuilderImpl.doAddDependency(ServiceBuilderImpl.java:216)
        at org.jboss.msc.service.ServiceBuilderImpl.addDependenciesNoCheck(ServiceBuilderImpl.java:158)
        at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:152)
        at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:142)
        at org.jboss.as.naming.deployment.JndiNamingDependencyProcessor.deploy(JndiNamingDependencyProcessor.java:59)
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
        ... 5 more

      The reason is that the INSTALL phase has six additional dependencies per EJB:

      • service jboss.naming.context.java.comp.example.example.<class-name>.InAppClientContainer
      • service jboss.naming.context.java.comp.example.example.<class-name>.InstanceName
      • service jboss.deployment.unit."example.jar".component.<class-name>.JndiBindingsService
      • service jboss.naming.context.java.comp.example.example.<class-name>.UserTransaction
      • service jboss.naming.context.java.comp.example.example.<class-name>.TransactionSynchronizationRegistry
      • service jboss.naming.context.java.comp.example.example.<class-name>.BeanManager

      We probably should not be creating N dependencies per deployment object since all the services of a given kind are always started together. They could be grouped at a deployment level instead.

      Attachments

        Issue Links

          is blocked 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) WFCORE-4390 Introduce COMPONENT_JNDI_DEPENDENCIES attachment key

          • 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.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15816 Too many services and dependencies created for EJBs

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          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) JBEAP-12237 [GSS](7.2.z) Too Many Dependencies Error occurs while deploying a large number of SLSBs to EAP 7

          • 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

          Activity

            People

              ropalka Richard Opalka
              dlloyd@redhat.com David Lloyd
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: