Bug 1500297 - [GSS] (6.4.z) Address DeploymentUnitProcessor leaks in the codebase
Summary: [GSS] (6.4.z) Address DeploymentUnitProcessor leaks in the codebase
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.4.17
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: CR1
: EAP 6.4.19
Assignee: Petr Jurak
QA Contact: Jiří Bílek
URL:
Whiteboard:
Depends On:
Blocks: eap6419-payload
TreeView+ depends on / blocked
 
Reported: 2017-10-10 11:02 UTC by tmiyargi
Modified: 2021-03-11 15:57 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-04-16 11:04:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-10787 0 Major Verified Address DeploymentUnitProcessor leaks in the codebase 2018-05-16 16:13:54 UTC
Red Hat Issue Tracker JBEAP-13851 0 Critical Pull Request Sent (7.0.z) Address DeploymentUnitProcessor leaks in the codebase 2018-05-16 16:13:54 UTC
Red Hat Issue Tracker WFLY-8697 0 Major Closed Address DeploymentUnitProcessor leaks in the codebase 2018-05-16 16:13:54 UTC
Red Hat Knowledge Base (Solution) 3211511 0 None None None 2017-10-13 17:40:03 UTC

Description tmiyargi 2017-10-10 11:02:22 UTC
Have 2 ears A and Z, A has a dependency (jboss-all) on Z, A has a singleton, startup scheduler, if I redeploy Z, A redeploys and fails with IllegalStateException:

16:40:05,470 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."jboss-javaee-sampletimer.ear"."jboss-javaee-sampletimer-ejb.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."jboss-javaee-sampletimer.ear"."jboss-javaee-sampletimer-ejb.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "jboss-javaee-sampletimer-ejb.jar" of deployment "jboss-javaee-sampletimer.ear"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014186: Failed to install management resources for ScheduleExample
	at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:82)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
	... 5 more
Caused by: java.lang.IllegalStateException
	at org.jboss.as.server.deployment.DeploymentModelUtils.getOrCreate(DeploymentModelUtils.java:100) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
	at org.jboss.as.server.deployment.DeploymentModelUtils.createDeploymentSubModel(DeploymentModelUtils.java:81) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
	at org.jboss.as.server.deployment.DeploymentUnitImpl.createDeploymentSubModel(DeploymentUnitImpl.java:104) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
	at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.installManagementResource(EjbManagementDeploymentUnitProcessor.java:118)
	at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:79)
	... 6 more


If I redeploy just A all works fine, the code in jboss-as-server-7.5.16.Final-redhat-1.jar indicates that the scheduler might still be somewhere:

if (parent.hasChild(element)) {
        if (desired == null) {
          return parent.requireChild(element);
        }
        throw new IllegalStateException();
      }

Upstream https://issues.jboss.org/browse/JBEAP-10787

Comment 3 Vladimir Dosoudil 2017-11-28 05:56:20 UTC
Upstream EAP 7.0: https://issues.jboss.org/browse/JBEAP-13851
Upstream EAP 7.1: https://issues.jboss.org/browse/JBEAP-10787
Upstream WildFly: https://issues.jboss.org/browse/WFLY-8697

Comment 4 Jiří Bílek 2018-01-11 10:43:35 UTC
Verified with EAP 6.4.19.CP.CR1


Note You need to log in before you can comment on or make changes to this bug.