[JBoss JIRA] (WFLY-13068) Error adding activemq-subsystem with outbound socket bindings
by Emmanuel Hugonnet (Jira)
Emmanuel Hugonnet created WFLY-13068:
----------------------------------------
Summary: Error adding activemq-subsystem with outbound socket bindings
Key: WFLY-13068
URL: https://issues.redhat.com/browse/WFLY-13068
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 19.0.0.Beta1
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.x-artemis2.x-ha-jdbc
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/362/artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean install -Dtest=org.jboss.qa.artemis.test.cli.attributes.RemoteBrokerCliAttributesTestCase#clientJmsQueueTest -Deap=7x | tee log
This is the error preventing the server to start:
18:47:41,968 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 70) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "messaging-activemq")]): java.lang.IllegalArgumentException: WFLYCTL0394: Capability 'org.wildfly.network.outbound-socket-binding.messaging-socket-binding' does not provide services of type 'null'
at org.jboss.as.controller.capability.RuntimeCapability.getCapabilityServiceName(RuntimeCapability.java:144) [wildfly-controller-11.0.0.Beta7.jar:11.0.0.Beta7]
at org.jboss.as.controller.capability.RuntimeCapability.getCapabilityServiceName(RuntimeCapability.java:198) [wildfly-controller-11.0.0.Beta7.jar:11.0.0.Beta7]
at org.jboss.as.controller.capability.RuntimeCapability.getCapabilityServiceName(RuntimeCapability.java:161) [wildfly-controller-11.0.0.Beta7.jar:11.0.0.Beta7]
at org.wildfly.extension.messaging.activemq.MessagingSubsystemAdd$2.execute(MessagingSubsystemAdd.java:178)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) [wildfly-controller-11.0.0.Beta7.jar:11.0.0.Beta7]
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) [wildfly-controller-11.0.0.Beta7.jar:11.0.0.Beta7]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) [wildfly-controller-11.0.0.Beta7.jar:11.0.0.Beta7]
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384) [wildfly-controller-11.0.0.Beta7.jar:11.0.0.Beta7]
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.3.Final.jar:2.3.3.Final]
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) [jboss-threads-2.3.3.Final.jar:2.3.3.Final]
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) [jboss-threads-2.3.3.Final.jar:2.3.3.Final]
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) [jboss-threads-2.3.3.Final.jar:2.3.3.Final]
at java.lang.Thread.run(Thread.java:818) [vm.jar:2.9 (08-02-2019)]
at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.3.Final.jar:2.3.3.Final]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-5017) DMN Validation does not provide a proper descriptive error message
by Duncan Doyle (Jira)
Duncan Doyle created DROOLS-5017:
------------------------------------
Summary: DMN Validation does not provide a proper descriptive error message
Key: DROOLS-5017
URL: https://issues.redhat.com/browse/DROOLS-5017
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.32.0.Final
Reporter: Duncan Doyle
Assignee: Michael Anstis
Attachments: Screenshot 2020-02-06 at 11.25.18.png, vacation-days.dmn
The attached DMN file is invalid as it contains a trailing space in one of its decision nodes (Base Vacation Days). I've checked with [~tari_manga], and according to him, the backend DMN validator is capable of detecting the problem and giving a proper error message. However the DMN editor in the workbench does not give any user friendly hint what the problem is, and hence it's almost impossible for a user to figure out what's wrong.
I've attached both the DMN model and a screenshot of the error message displayed by our editor.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFCORE-4835) [GSS](7.2.z) Write lock is acquired reading patching resource using include-runtime
by Ricardo Martin Camarero (Jira)
Ricardo Martin Camarero created WFCORE-4835:
-----------------------------------------------
Summary: [GSS](7.2.z) Write lock is acquired reading patching resource using include-runtime
Key: WFCORE-4835
URL: https://issues.redhat.com/browse/WFCORE-4835
Project: WildFly Core
Issue Type: Bug
Components: Patching
Reporter: Ricardo Martin Camarero
Assignee: Yeray Borges
Fix For: 11.0.0.Beta3
This is initially created as a bug but it needs first some investigation to discover if it is really necessary to acquire the write lock when the patching resource is read. If it is unnecessary, we should remove this need.
The following operation is acquiring the write lock:
{noformat}
/host=slave/core-service=patching:read-resource(include-runtime=true)
{noformat}
It potentially will block if there is any other operation that has already acquired the lock. One consequence found due to this issue was HAL could block and hang if an HC is starting and the user clicks on 'Patching' menu entry. It was fixed in HAL, where an HC being restarted is no longer shown in the Patching menu.
The main problem seems to be in PatchStreamResourceOperationStepHandler, which is the parent handler used for the handlers that manage patching operations. This parent handler is always acquiring the write lock.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFCORE-4834) Validate [GSS](7.2.z) composite operation steps just before executing them
by Ricardo Martin Camarero (Jira)
Ricardo Martin Camarero created WFCORE-4834:
-----------------------------------------------
Summary: Validate [GSS](7.2.z) composite operation steps just before executing them
Key: WFCORE-4834
URL: https://issues.redhat.com/browse/WFCORE-4834
Project: WildFly Core
Issue Type: Enhancement
Components: Management
Reporter: Ricardo Martin Camarero
Assignee: Yeray Borges
Fix For: 9.0.0.Beta7, 9.0.0.Final
Say we have a composite operation with 2 steps:
1) /extension=org.jboss.as.messaging:add
2) /subsystem=messaging:add
This will fail:
Failed to execute batch: JBAS014739: No handler for add at address
[("subsystem" => "messaging")]
This fails because at the time of validation the /subsystem=messaging:add is not valid.
To illustrate, the execution order is
Validate 1-2
1
2
A possible solution is to convert this to the following:
V1
1
V2 (works now because 1 has registered the subsystem API)
2
I think that should work but it's a very complex area, particularly in a managed domain, so it's not at all certain this would prove feasible.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months