Red Hat Issue Tracker

Red Hat Issue Tracker https://issues.redhat.com This file is an XML representation of an issue en-us

7.13.8

713008

13-09-2019

[AS7-244] ARQ tests using ArchiveDeployer may hang in deployment API https://issues.redhat.com/browse/AS7-244 Application Server 7 AS7-244

ARQ tests using ArchiveDeployer may hang in deployment API

Bug Major Resolved Done Thomas Diesler Thomas Diesler Wed, 13 Apr 2011 10:25:24 -0400 Thu, 21 Apr 2011 13:28:01 -0400 Mon, 18 Apr 2011 04:17:44 -0400 7.0.0.Beta3 0 4 Now using a timeout like this Future<ServerDeploymentPlanResult> future = deploymentManager.execute(plan); ServerDeploymentPlanResult planResult = future.get(5, TimeUnit.SECONDS); Run [tdiesler@localhost smoke]$ mvn -Pmodular-embedded -DskipTests -Dtest=ModuleAccessesBundleServiceTestCase test in <a href="https://github.com/jbosgi/jboss-as/tree/jbas9305" class="external-link" rel="nofollow">https://github.com/jbosgi/jboss-as/tree/jbas9305</a> I couldn't reproduce this, but Carlo could. It appears the issue was <a href="https://issues.redhat.com/browse/AS7-616" title="JBossAsManagedContainer prematurely thinks the AS is started" class="issue-link" data-issue-key="AS7-616"><del>JBAS-9312</del></a>, with <a href="https://issues.redhat.com/browse/AS7-298" title="Mgmt API access hangs for access to slaves when slave goes offline" class="issue-link" data-issue-key="AS7-298"><del>JBAS-9212</del></a> resulting in the failure getting swallowed. This one is slightly different from <a href="https://issues.redhat.com/browse/AS7-616" title="JBossAsManagedContainer prematurely thinks the AS is started" class="issue-link" data-issue-key="AS7-616"><del>JBAS-9312</del></a>. In case of a catastrophic failure no result is returned. <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>12:11:35,470 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) Starting deployment of "test-classes" 12:11:35,589 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit.test-classes.INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit.test-classes.INSTALL: Failed to process phase INSTALL of deployment "test-classes" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] Caused by: java.lang.NoClassDefFoundError: Ljavax/ejb/SessionContext; at java.lang.Class.getDeclaredFields0(Native Method) [:1.6.0_24] at java.lang.Class.privateGetDeclaredFields(Class.java:2291) [:1.6.0_24] at java.lang.Class.getDeclaredFields(Class.java:1743) [:1.6.0_24] at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:53) at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:65) at org.jboss.as.ee.component.AbstractComponentDescription.prepareComponentConfiguration(AbstractComponentDescription.java:392) at org.jboss.as.ejb3.component.session.SessionBeanComponentDescription.prepareComponentConfiguration(SessionBeanComponentDescription.java:346) at org.jboss.as.ee.component.AbstractComponentDescription.createComponentConfiguration(AbstractComponentDescription.java:363) at org.jboss.as.ee.component.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:104) at org.jboss.as.ee.component.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:67) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102) ... 4 more Caused by: java.lang.ClassNotFoundException: javax.ejb.SessionContext from [Module "deployment.test-classes:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:179) [jboss-modules-1.0.0.Beta18-SNAPSHOT.jar:1.0.0.Beta18-SNAPSHOT] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357) [jboss-modules-1.0.0.Beta18-SNAPSHOT.jar:1.0.0.Beta18-SNAPSHOT] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:329) [jboss-modules-1.0.0.Beta18-SNAPSHOT.jar:1.0.0.Beta18-SNAPSHOT] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306) [jboss-modules-1.0.0.Beta18-SNAPSHOT.jar:1.0.0.Beta18-SNAPSHOT] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100) [jboss-modules-1.0.0.Beta18-SNAPSHOT.jar:1.0.0.Beta18-SNAPSHOT] ... 15 more </pre> </div></div> (Don't read to much in the failure itself, it's an artificial construct.) It is probably not <a href="https://issues.redhat.com/browse/AS7-616" title="JBossAsManagedContainer prematurely thinks the AS is started" class="issue-link" data-issue-key="AS7-616"><del>JBAS-9312</del></a> because it happens in the middle of a test method execution. So ARQ is up, received the test request, executes the test method. During test method execution the injected ArchiveDeployer is used to install another test module. The test module's ServiceActivator is called and returns without failure (so the test module deployed and resolved ok). After that the mgmt API does not get notified that the deployment has finished. Thomas, I can reproduce this now. Carlo's divine spells lib (<a href="https://github.com/wolfc/jboss-as-divine-spells" class="external-link" rel="nofollow">https://github.com/wolfc/jboss-as-divine-spells</a>) shows the issue: pingguo:target bstansberry$ java -jar jboss-as-divine-spells.jar 16114 jboss.osgi.example.invoker.service -> jbosgi.systemcontext (**MISSING**) A missing dependency, resulting in the asynch processing of the deployment not making the necessary callback to the management layer to inform it of the result. This is what David Lloyd is working on for <a href="https://issues.redhat.com/browse/AS7-527" title="Provide more comprehensive error messages for missing dependencies" class="issue-link" data-issue-key="AS7-527"><del>JBAS-9010</del></a>. Carlo, your stack above is another manifestation of the same general problem – a problem with one of the many services associated with a deployment results in the callback not happening. I'll check with David whether he thinks his <a href="https://issues.redhat.com/browse/AS7-527" title="Provide more comprehensive error messages for missing dependencies" class="issue-link" data-issue-key="AS7-527"><del>JBAS-9010</del></a> work will deal with this kind of case as well. I believe its scope is more than just missing dependencies; it's also meant to deal with service failures. Brian Stansberry 9:11 AM carlo on <a href="https://issues.jboss.org/browse/JBAS-9305" class="external-link" rel="nofollow">https://issues.jboss.org/browse/JBAS-9305</a> has pasted a stack where a failure in start() results in the ResultHandler for a deployment op not getting called my impression is your 9010 stuff is dealing with failed services as well as missing deps David M. Lloyd 9:11 AM yes Fixed missing dependency Related AS7-616 AS7-298 SHRINKWRAP-269 Date of First Comment Thu, 14 Apr 2011 00:53:48 -0400 Development Number of attachments 2.0 Number of comments 9.0 Rank 1|hy6p7z: Rank (Obsolete) 28365 SFDC Cases Counter SFDC Cases Links Time in Status