[JBoss JIRA] (WFCORE-2746) Move elytron management security tests from core to full
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2746?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2746:
------------------------------------------
[~luck3y] Yes, a big part of this task is to remove the use of Arquillian from tests and use WildFly Test Runner.
HttpMgmtInterfaceElytronAuthenticationTestCase isn't merged yet as Ondrej mentioned. I made noise on that PR about just putting it in core in the first place or using WildFly Test Runner instead of ARQ, but I changed my mind since WFCORE-2747 means WTR isn't ready to handle that yet and I don't want to block getting the test in.
> Move elytron management security tests from core to full
> --------------------------------------------------------
>
> Key: WFCORE-2746
> URL: https://issues.jboss.org/browse/WFCORE-2746
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management, Security, Test Suite
> Reporter: Brian Stansberry
>
> Since until recently the elytron subsystem wasn't part of the core feature pack, a lot of integration tests of its use ended up in the WildFly full testsuite instead of in core. This task is to get tests that are only testing core functionality moved into the core testsuite. Because that's the right thing to do, but also because it's useful in practice by eliminating a cause for messy coordinated changes to core and full such that code changes in core can be tested.
> There are a number of aspects to this, for which I'll create subtasks.
> Following is an initial list of tests that should be moved. *This is meant to be a living list, with things added as they are noticed.* So anyone should feel free to edit this JIRA description to add things to the list.
> org.jboss.as.test.integration.security.perimeter.* [2]
> org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase
> org.jboss.as.test.integration.domain.AbstractSlaveHCAuthenticationTestCase and subclasses.[1]
> org.jboss.as.test.integration.security.credentialreference [2]
> [1] One subclass of this is not related to elytron but should be moved to core too. I haven't looked closely but it uses vault, which may be why it is in full. But we can use vault in the core testsuite now.
> [2] Currently using Arquillian.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (WFLY-8695) DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8695?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8695:
---------------------------------
Priority: Blocker (was: Major)
> DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-8695
> URL: https://issues.jboss.org/browse/WFLY-8695
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 11.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
>
> {noformat}
> 20:11:08,590 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
> 20:11:08,594 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
> 20:11:08,603 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel server: [node1|4] (1) [node1]
> ...
> 20:11:08,794 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started clusterbench-ee7-singleton-jbossall.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 20:11:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> 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: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
> at injection point [UnbackedAnnotatedField] @Inject private org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator
> at org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator(ValidationInterceptor.java:0)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:362)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
> at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:539)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:78)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:76)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[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:
-----------------------------------
Priority: Blocker (was: Critical)
> 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: Blocker
> Fix For: 3.0.0.Beta18
>
>
> {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, 8 months
[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:
-----------------------------------
Priority: Blocker (was: Major)
> 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
> Priority: Blocker
> 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, 8 months
[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:
-----------------------------------
Component/s: Server
> SubDeploymentProcessor leaks Attachments.SUB_DEPLOYMENTS on undeploy()
> ----------------------------------------------------------------------
>
> Key: WFCORE-2738
> URL: https://issues.jboss.org/browse/WFCORE-2738
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 3.0.0.Beta17
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
> Fix For: 3.0.0.Beta18
>
>
> {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, 8 months
[JBoss JIRA] (WFCORE-2691) Elytron modifiable realms should show existing identities in subsystem
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2691?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2691:
------------------------------------------
[~honza889] What about credential-store?
> Elytron modifiable realms should show existing identities in subsystem
> ----------------------------------------------------------------------
>
> Key: WFCORE-2691
> URL: https://issues.jboss.org/browse/WFCORE-2691
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta15
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Blocker
> Labels: filesystem-realm, security-realm
>
> Elytron {{filesystem-realm}} should load existing identities from file system. The steps to reproduce results in:
> {noformat}
> [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:read-identity
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"elytron\"),
> (\"filesystem-realm\" => \"realm\"),
> (\"identity\" => \"user\")
> ]' not found",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:add
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY01000: Identity with name [user] already exists.",
> "rolled-back" => true
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (WFLY-8695) DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8695?page=com.atlassian.jira.plugin.... ]
Radoslav Husar moved WFCORE-2757 to WFLY-8695:
----------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-8695 (was: WFCORE-2757)
Component/s: CDI / Weld
(was: Server)
Affects Version/s: (was: 3.0.0.Beta17)
> DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-8695
> URL: https://issues.jboss.org/browse/WFLY-8695
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> {noformat}
> 20:11:08,590 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
> 20:11:08,594 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
> 20:11:08,603 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel server: [node1|4] (1) [node1]
> ...
> 20:11:08,794 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started clusterbench-ee7-singleton-jbossall.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 20:11:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> 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: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
> at injection point [UnbackedAnnotatedField] @Inject private org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator
> at org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator(ValidationInterceptor.java:0)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:362)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
> at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:539)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:78)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:76)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (WFLY-8695) DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8695?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8695:
---------------------------------
Affects Version/s: 11.0.0.Alpha1
> DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-8695
> URL: https://issues.jboss.org/browse/WFLY-8695
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 11.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> {noformat}
> 20:11:08,590 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
> 20:11:08,594 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
> 20:11:08,603 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel server: [node1|4] (1) [node1]
> ...
> 20:11:08,794 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started clusterbench-ee7-singleton-jbossall.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 20:11:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> 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: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default
> at injection point [UnbackedAnnotatedField] @Inject private org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator
> at org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator(ValidationInterceptor.java:0)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:362)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
> at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:539)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:78)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:76)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months