Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-5947

EAR deployment may exhaust service threads and fail

    XMLWordPrintable

Details

    Description

      Sergiy reports a problem with an EAR deployment that contains 50+ bundle deployments. The EAR deployment fails because of msc thread exhaustion.

      We can reproduce this with the simple OSGi EnterpriseArchiveTestCase when setting -Dorg.jboss.server.bootstrap.maxThreads=1

      08:44:59,723 INFO  [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011002: Bundle started: osgi-ear-test:0.0.0
      08:44:59,829 INFO  [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "osgi-ear-test"
      08:44:59,908 INFO  [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location /home/tdiesler/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/3f/c71a8405efa7c357109e2a8627448b851fc9f2/content
      08:44:59,912 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "simple.ear"
      08:44:59,933 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "simple.war"
      08:45:00,251 INFO  [org.jboss.web] (MSC service thread 1-1) JBAS018210: Register web context: /simple
      08:45:00,479 INFO  [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "simple.ear"
      08:45:00,569 INFO  [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/tdiesler/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/75/2868c1b3add99cf61f8cc648c666c0f89c90ba/content
      08:45:00,571 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "war-structure.ear"
      08:45:00,581 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "echo-bundle.jar"
      08:45:00,582 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "war-structure-bundle.war"
      08:45:00,609 INFO  [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: echo-bundle.jar:0.0.0
      08:45:00,616 INFO  [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: war-structure-bundle.war:0.0.0
      08:45:00,625 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015970: Defer FIRST_MODULE_USE for war-structure.ear making it LAZY
      08:45:00,628 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015970: Defer FIRST_MODULE_USE for echo-bundle.jar making it PASSIVE
      08:45:02,676 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.module.service."deployment.war-structure.ear.war-structure-bundle.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.war-structure.ear.war-structure-bundle.war".main: JBAS018759: Failed to load module: deployment.war-structure.ear.war-structure-bundle.war:main
      	at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:92) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
      	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
      	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
      Caused by: org.jboss.modules.ModuleLoadException: JBAS018760: Timeout waiting for module service: deployment.war-structure.ear:main
      	at org.jboss.as.server.moduleservice.ServiceModuleLoader$ModuleSpecLoadListener.getModuleSpec(ServiceModuleLoader.java:133) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
      	at org.jboss.as.server.moduleservice.ServiceModuleLoader.findModule(ServiceModuleLoader.java:174) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
      	at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) [jboss-modules.jar:1.1.3.GA]
      	at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) [jboss-modules.jar:1.1.3.GA]
      	at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloadModule(ServiceModuleLoader.java:158) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
      	at org.jboss.modules.Module.addPaths(Module.java:851) [jboss-modules.jar:1.1.3.GA]
      	at org.jboss.modules.Module.link(Module.java:1206) [jboss-modules.jar:1.1.3.GA]
      	at org.jboss.modules.Module.relinkIfNecessary(Module.java:1235) [jboss-modules.jar:1.1.3.GA]
      	at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) [jboss-modules.jar:1.1.3.GA]
      	at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:71) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
      	... 5 more
      
      08:45:02,802 ERROR [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "war-structure.ear" was rolled back with the following failure message: "JBAS014750: Operation handler failed to complete"
      

      The same test works fine with -Dorg.jboss.server.bootstrap.maxThreads=2

      Attachments

        Activity

          People

            tdiesler@redhat.com Thomas Diesler
            tdiesler@redhat.com Thomas Diesler
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: