[JBoss JIRA] (WFLY-10248) write to jgroups-channel throws IllegalStateException
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10248?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-10248:
-----------------------------------------
I don't understand what 'ejb' or 'ee' has to do with this. But reading Paul's last comment carefully I don't think he thinks it does either.
So this comment is probably just for the record so later readers don't get mistaken.
{code}
java.lang.IllegalStateException: WFLYCTL0365: Capability 'org.wildfly.messaging.activemq.discovery-group.my_disco' is unknown in context 'profile=full-ha'.
at org.jboss.as.controller.CapabilityRegistry.registerRequirement(CapabilityRegistry.java:212)
{code}
That means that a requirement that capability org.wildfly.messaging.activemq.discovery-group.my_disco wants to add is being rejected because the system doesn't recognize org.wildfly.messaging.activemq.discovery-group.my_disco as even being a capability. A non-existent cap can't require anything, and if one tries we have a software bug and not a user mistake. That is why this produces an ugly ISE in the logs and not just a normal mgmt op failure telling the user that their config has an incorrect reference and suggesting how to fix it.
> write to jgroups-channel throws IllegalStateException
> -----------------------------------------------------
>
> Key: WFLY-10248
> URL: https://issues.jboss.org/browse/WFLY-10248
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Claudio Miranda
> Assignee: Paul Ferraro
>
> {code}
> /profile=full-ha/subsystem=messaging-activemq/server=default/discovery-group=my_disco:add(jgroups-channel=ee,jgroups-cluster=disco)
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => {"other-server-group" => {"host" => {"master" => {"server-three" => {"response" => {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }}}}}}
> }
> [domain@uranus-0:9990 /] reload --host=master
> {code}
> reload host master, success
> Then, try to replace jgroups-channel value "ee" to "ejb", as its suggested by capability-reference
> {code}
> /profile=full-ha/subsystem=messaging-activemq/server=default/discovery-group=my_disco:write-attribute(name=jgroups-channel,value=ejb)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0365: Capability 'org.wildfly.messaging.activemq.discovery-group.my_disco' is unknown in context 'profile=full-ha'."},
> "rolled-back" => true
> }
> {code}
> {code}
> 2018-04-16 16:10:31,044 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
> ("profile" => "full-ha"),
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("discovery-group" => "my_disco")
> ]): java.lang.IllegalStateException: WFLYCTL0365: Capability 'org.wildfly.messaging.activemq.discovery-group.my_disco' is unknown in context 'profile=full-ha'.
> at org.jboss.as.controller.CapabilityRegistry.registerRequirement(CapabilityRegistry.java:212)
> at org.jboss.as.controller.CapabilityRegistry.registerAdditionalCapabilityRequirement(CapabilityRegistry.java:198)
> at org.jboss.as.controller.OperationContextImpl.registerAdditionalCapabilityRequirement(OperationContextImpl.java:1520)
> at org.jboss.as.controller.OperationContextImpl.registerAdditionalCapabilityRequirement(OperationContextImpl.java:1512)
> at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.processCapabilityRequirement(CapabilityReferenceRecorder.java:137)
> at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.addCapabilityRequirements(CapabilityReferenceRecorder.java:114)
> at org.jboss.as.controller.AttributeDefinition.addCapabilityRequirements(AttributeDefinition.java:1066)
> at org.jboss.as.controller.AbstractWriteAttributeHandler.recordCapabilitiesAndRequirements(AbstractWriteAttributeHandler.java:191)
> at org.jboss.as.controller.AbstractWriteAttributeHandler.execute(AbstractWriteAttributeHandler.java:89)
> at org.jboss.as.controller.operations.global.WriteAttributeHandler.doExecuteInternal(WriteAttributeHandler.java:194)
> at org.jboss.as.controller.operations.global.WriteAttributeHandler.execute(WriteAttributeHandler.java:115)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10246) Required services that are not installed
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10246?page=com.atlassian.jira.plugin... ]
Brian Stansberry resolved WFLY-10246.
-------------------------------------
Assignee: Brian Stansberry (was: Jason Greene)
Resolution: Rejected
Great; I'm glad you found a solution.
I'm rejecting this as there's WildFly no bug. I wish our JIRA had a differently named equivalent to "Rejected", it sounds so harsh!
> Required services that are not installed
> ----------------------------------------
>
> Key: WFLY-10246
> URL: https://issues.jboss.org/browse/WFLY-10246
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Environment: migrating wildfly 10.1.0 to widfly-swarm 2017.11.0
> Reporter: Zakaria mh
> Assignee: Brian Stansberry
> Labels: Swarm
>
> ERROR [org.jboss.as.controller.management-operation] (main) WFLYCTL0013: Operation ("add") failed - address: (("deployment" => "module1-3.3.0-SNAPSHOT.war")) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"module1-3.3.0-SNAPSHOT.war\".PARSE is missing [jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService]"]
> }
> [0m [31m2018-04-16 12:13:59,010 ERROR [org.jboss.as.server] (main) WFLYSRV0021: Deploy of deployment "module1-3.3.0-SNAPSHOT.war" was rolled back with the following failure message:
> {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"module1-3.3.0-SNAPSHOT.war\".PARSE is missing [jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService]"]
> }
> [0m [0m2018-04-16 12:13:59,789 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment module1-3.3.0-SNAPSHOT.war (runtime-name: module1-3.3.0-SNAPSHOT.war) in 779ms
> [0m [0m2018-04-16 12:13:59,790 INFO [org.jboss.as.controller] (main) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."module2D-3.3.0-SNAPSHOT.ear".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."module1-3.3.0-SNAPSHOT.war".PARSE]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo commented on SWSQE-113:
-----------------------------------------------
OK.
Marking this issue as resolved for time being.
> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
> Key: SWSQE-113
> URL: https://issues.jboss.org/browse/SWSQE-113
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet.
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo resolved SWSQE-113.
-------------------------------------------
Resolution: Done
> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
> Key: SWSQE-113
> URL: https://issues.jboss.org/browse/SWSQE-113
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet.
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years