February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5017) DMN Validation does not provide a proper descriptive error message

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5017?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5017: ---------------------------------------- > the error messages suggests KIE's DMN validation barfed I beg to differ, looks to me more a kie compilation attempted before the VALIDATE_MODEL have a chance of being executed. > 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 > Priority: Major > Labels: drools-tools > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4024) Move keyboard shortcuts to menus in DMN.

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4024?page=com.atlassian.jira.plug... ] Guilherme Gomes commented on DROOLS-4024: ----------------------------------------- Yes, [~jomarko] IIUC this JIRA I was fix by https://github.com/kiegroup/kie-wb-common/pull/3125. [~uxdlc], may we close this JIRA? :-) Thanks! > Move keyboard shortcuts to menus in DMN. > ---------------------------------------- > > Key: DROOLS-4024 > URL: https://issues.redhat.com/browse/DROOLS-4024 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: currentMenu.png, insert+.png, kebab-shortcuts.png > > > As a business analyst practitioner, I would like to view the keyboard shortcuts in the context of the menu actions that they refer to. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5017) DMN Validation does not provide a proper descriptive error message

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5017?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5017: ---------------------------------------- Well.. the error messages suggests KIE's DMN validation barfed when trying to validate the model... I will however investigate and report back soon. > 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 > Priority: Major > Labels: drools-tools > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5017) DMN Validation does not provide a proper descriptive error message

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5017?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5017: ---------------------------------------- The validator reports the following messages: {code:java} Message [id=0, level=WARNING, path=null, line=108, column=-1 text=DMN: Variable name contains leading or traling spaces 'Base Vacation Days ' on node 'Base Vacation Days ' (DMN id: _34B27FCC-31C7-419B-85D4-63F8E6B8DD71, The listed name is not a valid FEEL identifier) ] Message [id=0, level=WARNING, path=null, line=137, column=-1 text=DMN: Decision table with single output on node 'Extra days case 1' should not have an output type reference (DMN id: _0CD749C5-FABA-4A0C-9AAF-C44AC9D19CE2, The referenced element should not have a typeref set) ] Message [id=0, level=WARNING, path=null, line=77, column=-1 text=DMN: Decision table with single output on node 'Extra days case 3' should not have an output type reference (DMN id: _F385BCF6-3C6E-464A-B5D8-8B74F0985421, The referenced element should not have a typeref set) ] Message [id=0, level=WARNING, path=null, line=24, column=-1 text=DMN: Decision table with single output on node 'Extra days case 2' should not have an output type reference (DMN id: _5F5AF524-E9FF-4DC4-8609-18093C4D1C47, The referenced element should not have a typeref set) ] {code} > 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 > Priority: Major > Labels: drools-tools > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5017) DMN Validation does not provide a proper descriptive error message

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5017?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5017: ----------------------------------- Labels: drools-tools (was: ) > 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 > Priority: Major > Labels: drools-tools > 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)

6 years, 5 months

1
0
0 / 0

[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)

6 years, 5 months

1
0
0 / 0

[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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2449) TCP/UDP: buffer size of 0 will not set buffer sizes

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2449?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2449: -------------------------------- I don't like -1; I'll use 0. > TCP/UDP: buffer size of 0 will not set buffer sizes > --------------------------------------------------- > > Key: JGRP-2449 > URL: https://issues.redhat.com/browse/JGRP-2449 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.0 > > > If we set (e.g.) {{mcast_recv_buf_size}} to {{0}}, then we won't set the buffer size, but will use whatever the OS default is. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[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)

6 years, 5 months

1
0
0 / 0

[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)

6 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2020