[JBoss JIRA] (WFCORE-2750) ModuleSpecProcessor does not recreate module spec after undeploy
by Radoslav Husar (JIRA)
Radoslav Husar created WFCORE-2750:
--------------------------------------
Summary: ModuleSpecProcessor does not recreate module spec after undeploy
Key: WFCORE-2750
URL: https://issues.jboss.org/browse/WFCORE-2750
Project: WildFly Core
Issue Type: Bug
Components: Server
Affects Versions: 3.0.0.Beta17
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Fix For: 3.0.0.Beta18
Block singleton deployments. Hangs after
{noformat}23:40:37,420 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node1 elected as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
23:40:37,424 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
23:40:37,435 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel server: [node1|4] (1) [node1]
23:40:37,436 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel web: [node1|4] (1) [node1]
23:40:37,436 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel ejb: [node1|4] (1) [node1]
23:40:37,437 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel hibernate: [node1|4] (1) [node1]
23:40:37,451 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "clusterbench-ee7-web-passivating.war")
23:40:37,451 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "clusterbench-ee7-web-default.war")
23:40:37,451 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "clusterbench-ee7-ejb.jar")
{noformat}
due to unsatisfied dependencies
{noformat}19:18:40,907 INFO [stdout] (MSC service thread 1-1) Service "jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".FIRST_MODULE_USE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".CONFIGURE_MODULE) (dependencies: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".CONFIGURE_MODULE, jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main, jboss.deployment.chains, jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (has unavailable dependency)
19:18:40,908 INFO [stdout] (MSC service thread 1-1) Service "jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".FIRST_MODULE_USE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".CONFIGURE_MODULE) (dependencies: jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main, jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".CONFIGURE_MODULE, jboss.deployment.chains, jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (has unavailable dependency)
19:18:40,908 INFO [stdout] (MSC service thread 1-1) Service "jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".FIRST_MODULE_USE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".CONFIGURE_MODULE) (dependencies: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".CONFIGURE_MODULE, jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main, jboss.deployment.chains, jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (has unavailable dependency)
19:18:40,908 INFO [stdout] (MSC service thread 1-1) Service "jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".POST_MODULE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (dependencies: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".FIRST_MODULE_USE, jboss.deployment.chains, jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".FIRST_MODULE_USE, jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".FIRST_MODULE_USE, jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (has unavailable dependency)
19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main.1" (class org.jboss.as.server.moduleservice.ModuleResolvePhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main.0) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main) (has unavailable dependency)
19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main.1" (class org.jboss.as.server.moduleservice.ModuleResolvePhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main.0) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main) (has unavailable dependency)
19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main.1" (class org.jboss.as.server.moduleservice.ModuleResolvePhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main.0) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main) (has unavailable dependency)
19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main" (class org.jboss.as.server.moduleservice.ModuleLoadService) mode ON_DEMAND state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".CONFIGURE_MODULE) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, module.resolved.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main, jboss.as.service-module-loader, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main) (has unavailable dependency)
19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main" (class org.jboss.as.server.moduleservice.ModuleLoadService) mode ON_DEMAND state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".CONFIGURE_MODULE) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, module.resolved.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main, jboss.as.service-module-loader, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main) (has unavailable dependency)
19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main" (class org.jboss.as.server.moduleservice.ModuleLoadService) mode ON_DEMAND state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".CONFIGURE_MODULE) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, jboss.as.service-module-loader, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main, module.resolved.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main) (has unavailable dependency)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (WFCORE-2750) ModuleSpecProcessor does not recreate module spec after undeploy()
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2750?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFCORE-2750:
-----------------------------------
Summary: ModuleSpecProcessor does not recreate module spec after undeploy() (was: ModuleSpecProcessor does not recreate module spec after undeploy)
> ModuleSpecProcessor does not recreate module spec after undeploy()
> ------------------------------------------------------------------
>
> Key: WFCORE-2750
> URL: https://issues.jboss.org/browse/WFCORE-2750
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 3.0.0.Beta17
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 3.0.0.Beta18
>
>
> Block singleton deployments. Hangs after
> {noformat}23:40:37,420 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node1 elected as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
> 23:40:37,424 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
> 23:40:37,435 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel server: [node1|4] (1) [node1]
> 23:40:37,436 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel web: [node1|4] (1) [node1]
> 23:40:37,436 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel ejb: [node1|4] (1) [node1]
> 23:40:37,437 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel hibernate: [node1|4] (1) [node1]
> 23:40:37,451 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "clusterbench-ee7-web-passivating.war")
> 23:40:37,451 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "clusterbench-ee7-web-default.war")
> 23:40:37,451 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "clusterbench-ee7-ejb.jar")
> {noformat}
> due to unsatisfied dependencies
> {noformat}19:18:40,907 INFO [stdout] (MSC service thread 1-1) Service "jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".FIRST_MODULE_USE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".CONFIGURE_MODULE) (dependencies: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".CONFIGURE_MODULE, jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main, jboss.deployment.chains, jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (has unavailable dependency)
> 19:18:40,908 INFO [stdout] (MSC service thread 1-1) Service "jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".FIRST_MODULE_USE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".CONFIGURE_MODULE) (dependencies: jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main, jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".CONFIGURE_MODULE, jboss.deployment.chains, jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (has unavailable dependency)
> 19:18:40,908 INFO [stdout] (MSC service thread 1-1) Service "jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".FIRST_MODULE_USE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".CONFIGURE_MODULE) (dependencies: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".CONFIGURE_MODULE, jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main, jboss.deployment.chains, jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (has unavailable dependency)
> 19:18:40,908 INFO [stdout] (MSC service thread 1-1) Service "jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".POST_MODULE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (dependencies: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".FIRST_MODULE_USE, jboss.deployment.chains, jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".FIRST_MODULE_USE, jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".FIRST_MODULE_USE, jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".FIRST_MODULE_USE) (has unavailable dependency)
> 19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main.1" (class org.jboss.as.server.moduleservice.ModuleResolvePhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main.0) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main) (has unavailable dependency)
> 19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main.1" (class org.jboss.as.server.moduleservice.ModuleResolvePhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main.0) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main) (has unavailable dependency)
> 19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main.1" (class org.jboss.as.server.moduleservice.ModuleResolvePhaseService) mode ACTIVE state DOWN (PROBLEM) (parent: jboss.module.resolve.phase."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main.0) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main) (has unavailable dependency)
> 19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main" (class org.jboss.as.server.moduleservice.ModuleLoadService) mode ON_DEMAND state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-ejb.jar".CONFIGURE_MODULE) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, module.resolved.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main, jboss.as.service-module-loader, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main) (has unavailable dependency)
> 19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main" (class org.jboss.as.server.moduleservice.ModuleLoadService) mode ON_DEMAND state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-default.war".CONFIGURE_MODULE) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, module.resolved.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main, jboss.as.service-module-loader, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-default.war".main, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main) (has unavailable dependency)
> 19:18:40,925 INFO [stdout] (MSC service thread 1-1) Service "jboss.module.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main" (class org.jboss.as.server.moduleservice.ModuleLoadService) mode ON_DEMAND state DOWN (PROBLEM) (parent: jboss.deployment.subunit."clusterbench-ee7-singleton-jbossall.ear"."clusterbench-ee7-web-passivating.war".CONFIGURE_MODULE) (dependencies: jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear".main, jboss.as.service-module-loader, jboss.module.spec.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-ejb.jar".main, module.resolved.service."deployment.clusterbench-ee7-singleton-jbossall.ear.clusterbench-ee7-web-passivating.war".main) (has unavailable dependency)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (WFCORE-2738) SubDeploymentProcessor leaks Attachments.SUB_DEPLOYMENTS on undeploy()
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2738?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFCORE-2738:
-----------------------------------
Summary: SubDeploymentProcessor leaks Attachments.SUB_DEPLOYMENTS on undeploy() (was: SubDeploymentProcessor leaks Attachments.SUB_DEPLOYMENTS on undeploy)
> SubDeploymentProcessor leaks Attachments.SUB_DEPLOYMENTS on undeploy()
> ----------------------------------------------------------------------
>
> Key: WFCORE-2738
> URL: https://issues.jboss.org/browse/WFCORE-2738
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta17
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
>
> {noformat}
> 19:33:36,944 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "clusterbench-ee7-singleton-jbossall.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> 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:745)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.deployment.module.SubDeploymentDependencyProcessor.deploy(SubDeploymentDependencyProcessor.java:74)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (WFCORE-2738) SubDeploymentProcessor leaks Attachments.SUB_DEPLOYMENTS on undeploy
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2738?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFCORE-2738:
-----------------------------------
Summary: SubDeploymentProcessor leaks Attachments.SUB_DEPLOYMENTS on undeploy (was: Attachments.SUB_DEPLOYMENTS leaks on undeploy)
> SubDeploymentProcessor leaks Attachments.SUB_DEPLOYMENTS on undeploy
> --------------------------------------------------------------------
>
> Key: WFCORE-2738
> URL: https://issues.jboss.org/browse/WFCORE-2738
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta17
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
>
> {noformat}
> 19:33:36,944 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "clusterbench-ee7-singleton-jbossall.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> 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:745)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.deployment.module.SubDeploymentDependencyProcessor.deploy(SubDeploymentDependencyProcessor.java:74)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (WFCORE-13) End users can call non-published management API operations
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-13?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFCORE-13:
----------------------------------------
Uses of SimpleOperationDefinitionBuilder.setPrivateEntry(), with a note for each re whether there are any concerns with preventing outside execution:
controller/src/main/java/org/jboss/as/controller/AbstractControllerService.java: INIT_CONTROLLER_OP (ok)
controller/src/main/java/org/jboss/as/controller/CompositeOperationHandler.java: INTERNAL_DEFINITION (ok)
controller/src/main/java/org/jboss/as/controller/operations/common/GenericSubsystemDescribeHandler.java: (consider 'hidden')
controller/src/main/java/org/jboss/as/controller/operations/common/ValidateOperationHandler.java: DEFINITION_PRIVATE (ok)
controller/src/main/java/org/jboss/as/controller/operations/global/ReadResourceDescriptionHandler.java: CheckResourceAccessHandler (ok)
controller/src/main/java/org/jboss/as/controller/registry/ProxyControllerRegistration.java: ProxyStepHandler (ok)
controller/src/main/java/org/jboss/as/controller/transform/SubsystemDescriptionDump.java: (consider 'hidden')
controller/src/test/java/org/jboss/as/controller/notification/NotificationCompositeOperationTestCase.java: (test)
controller/src/test/java/org/jboss/as/controller/notification/OperationWithManyStepsTestCase.java: (test)
controller/src/test/java/org/jboss/as/controller/notification/OperationWithNotificationTestCase.java: (test)
controller/src/test/java/org/jboss/as/controller/test/CastAttributeOperationTestCase.java: (test)
controller/src/test/java/org/jboss/as/controller/test/ReadResourceChildOrderingTestCase.java: (test)
controller/src/test/java/org/jboss/as/controller/test/TestUtils.java: (test)
controller/src/test/java/org/jboss/as/controller/test/WriteAttributeOperationTestCase.java: (test)
domain-management/src/main/java/org/jboss/as/domain/management/access/AccessAuthorizationDomainSlaveConfigHandler.java: (ok)
host-controller/src/main/java/org/jboss/as/domain/controller/operations/ApplyExtensionsHandler.java: (ok)
host-controller/src/main/java/org/jboss/as/domain/controller/operations/GenericModelDescribeOperationHandler.java: (consider 'hidden')
host-controller/src/main/java/org/jboss/as/domain/controller/operations/ReadMasterDomainOperationsHandler.java: (ok)
host-controller/src/main/java/org/jboss/as/domain/controller/resources/ProfileResourceDefinition.java: DESCRIBE (consider 'hidden')
host-controller/src/main/java/org/jboss/as/host/controller/operations/HostModelRegistrationHandler.java: (ok)
host-controller/src/main/java/org/jboss/as/host/controller/operations/InstallationReportHandler.java: (ok)
host-controller/src/main/java/org/jboss/as/host/controller/operations/StartServersHandler.java: (ok)
host-controller/src/main/java/org/jboss/as/host/controller/resources/StoppedServerResource.java: (unused; remove)
server/src/main/java/org/jboss/as/server/DeployerChainAddHandler.java: (ok)
server/src/main/java/org/jboss/as/server/operations/InstallationReportHandler.java: (ok)
server/src/main/java/org/jboss/as/server/operations/ServerDomainProcessReloadHandler.java: (ok)
server/src/main/java/org/jboss/as/server/operations/ServerDomainProcessShutdownHandler.java: (ok)
server/src/main/java/org/jboss/as/server/operations/ServerProcessStateHandler.java: (should be ok but may have to use 'hidden' as this op was documented)
server/src/main/java/org/jboss/as/server/operations/ServerProcessStateHandler.java: (should be ok but may have to use 'hidden' as this op was documented)
server/src/main/java/org/jboss/as/server/operations/ServerResumeHandler.java: DOMAIN_DEFINITION (ok)
server/src/main/java/org/jboss/as/server/operations/ServerSuspendHandler.java: DOMAIN_DEFINITION (ok)
server/src/main/java/org/jboss/as/server/operations/SetServerGroupHostHandler.java: (ok)
subsystem-test/framework/src/main/java/org/jboss/as/subsystem/test/ReadTransformedResourceOperation.java: (test)
By "consider 'hidden'" in the notes above, I mean a new flag on the operation entry that would result in the current behavior of setPrivateEntry -- i.e. the op is not described in the API but will work if invoked. This is basically meant for things that we suspect people may be using and we don't want to break them, but where don't want to commit to the op as part of the published API.
> End users can call non-published management API operations
> ----------------------------------------------------------
>
> Key: WFCORE-13
> URL: https://issues.jboss.org/browse/WFCORE-13
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Ladislav Thon
> Labels: EAP
>
> It's not possible to call "non-published" operations (those that are not visible in the resource tree, e.g. {{describe}}) via JMX, while it's entirely possible to call them via CLI (e.g. {{/subsystem=security:describe}}) and other management interfaces.
> The problem lies in the fact that {{ModelControllerMBeanHelper.invoke}} method checks {{if (!accessControl.isExecutableOperation(operationName))}} and the {{isExecutableOperation}} method assumes that the operation will be visible in the resource tree. In fact, there is a comment stating _should not happen_, but now we know that it indeed _can_ happen.
> What's more, it gives a misleading error message. The {{isExecutableOperation}} returns {{false}} for unknown operations, which results in {{Not authorized to invoke operation}} message. Which is wrong in two different ways simultaneously: 1. the problem isn't authorization, but the fact that the operation can't be found; 2. the user (e.g. in the {{SuperUser}} role) _is_ authorized.
> I'm considering this low priority, because 1. JMX is likely to be very rarely used to access the management interface, 2. hiding information isn't nearly as important as leaking them, 3. non-published operations aren't nearly as important as the published ones. It's worth a JIRA nevertheless.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years