July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5541) Exception thrown after creating a DMN File on a new Project

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5541?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5541: ----------------------------------- Component/s: core engine (was: DMN Editor) (was: Guided Decision Table Editor) > Exception thrown after creating a DMN File on a new Project > ----------------------------------------------------------- > > Key: DROOLS-5541 > URL: https://issues.redhat.com/browse/DROOLS-5541 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.41.0.Final > Reporter: Yeser Amer > Assignee: Daniele Zonca > Priority: Major > Attachments: Screencast from 07-29-2020.webm, Screenshot from 2020-07-29 10-06-49.png, Screenshot from 2020-07-29 10-07-05.png, stacktrace.txt > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5541) Exception thrown after creating a DMN File on a new Project

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5541?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-5541: -------------------------------------- Assignee: Daniele Zonca (was: Guilherme Gomes) > Exception thrown after creating a DMN File on a new Project > ----------------------------------------------------------- > > Key: DROOLS-5541 > URL: https://issues.redhat.com/browse/DROOLS-5541 > Project: Drools > Issue Type: Bug > Components: DMN Editor, Guided Decision Table Editor > Affects Versions: 7.41.0.Final > Reporter: Yeser Amer > Assignee: Daniele Zonca > Priority: Major > Attachments: Screencast from 07-29-2020.webm, Screenshot from 2020-07-29 10-06-49.png, Screenshot from 2020-07-29 10-07-05.png, stacktrace.txt > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5235) An existing decision table already binding an object doesn't see when a field is added to that object

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5235?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-5235: ------------------------------------ Assignee: Toni Rikkola (was: Michael Anstis) > An existing decision table already binding an object doesn't see when a field is added to that object > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-5235 > URL: https://issues.redhat.com/browse/DROOLS-5235 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Mario Fusco > Assignee: Toni Rikkola > Priority: Major > > Steps to reproduce: > 1. Create a data object with a few fields > 2. Create a Guided decision table with at least a condition column binding that object > 3. Go back to the object definition and add a new field and save > 4. Go back to the decision table and add a second column condition on the same object: the newly added field is not available among the other old fields in the drop down menu > Note that if you create a brand new table and try to add a condition on that object than also the new field is available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5090) enumeration values used in rules can be deleted

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5090?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-5090: ------------------------------------ Assignee: Toni Rikkola (was: Michael Anstis) > enumeration values used in rules can be deleted > ----------------------------------------------- > > Key: DROOLS-5090 > URL: https://issues.redhat.com/browse/DROOLS-5090 > Project: Drools > Issue Type: Bug > Components: Enumerations Editor > Reporter: Werner Van Herrewegen > Assignee: Toni Rikkola > Priority: Major > > As a rule creator, > whenever the value list of an enumeration gets modified, I want to make sure that no rules are broken because of it. > NOW IT IS BROKEN: > see steps to reproduce > solution suggestion: > prevent the deletion of an enumeration value when it is in use in a rule > The user should be made aware what rule(s) is/are blocking the removal of a value! > --> the user must first 'prepare' the rules and then come back to remove the value from the list > ATTENTION: > This logic only is valid for DELETION/RENAMING of enumeration values, > Rearranging values and adding values can happen without any problem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5091) purpose and/or howtouse instruction on guided decision tables

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5091?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-5091: ------------------------------------ Assignee: Toni Rikkola (was: Michael Anstis) > purpose and/or howtouse instruction on guided decision tables > ------------------------------------------------------------- > > Key: DROOLS-5091 > URL: https://issues.redhat.com/browse/DROOLS-5091 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Werner Van Herrewegen > Assignee: Toni Rikkola > Priority: Minor > > As a rule creator I want to have my instructions on how to use and what values are expected to be entered in the cells of a decision table on the same page as where a business user will fill in the values in the columns. > Business people usually only fill in the decision tables so I limit my scope to guided decision tables. > I would like to have a read-only copy of the (already existing) overview>comments field at the top of guided decision tables 'model view'. > Only if the text box contains something > root cause for this demand is that : > * business people want to do as much as possible in ONE grid view (familiar with excel :-) ) > * business central allows to do this by adding columns that are not relevant for some rule rows and relevant for other rule rows. (leaving the cell empty removes that rule line in the generated drl code) > * some combinations are not allowed > * and no way to enforce/prevent the allowed/forbidden combinations > * It would be nice as a rule builder to add this 'dummy proofing invalid column combinations) to the guided decision tables config data -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2722) [Guided Decision Tree] Unable to drag model to Decision tree when the model is huge

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-2722?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-2722: ------------------------------------ Assignee: Toni Rikkola (was: Michael Anstis) > [Guided Decision Tree] Unable to drag model to Decision tree when the model is huge > ----------------------------------------------------------------------------------- > > Key: DROOLS-2722 > URL: https://issues.redhat.com/browse/DROOLS-2722 > Project: Drools > Issue Type: Bug > Components: Guided Decision Tree Editor > Affects Versions: 7.8.0.Final > Reporter: How Fong Hew > Assignee: Toni Rikkola > Priority: Major > Attachments: unable to drag model to decision tree.gif > > > *Problem:* > When the list of properties/attributes in a particular model are huge (more than 20), not able to drag the last property of the model to the decision tree after scrolling down to the page where the property reside. > *Steps to Reproduce:* > * Refer to the attached file “unable to drag model to decision tree.gif” > * Expand all the model in the Guided Decision Trees > * Unable to drag and add the bottom property to the decision > *Expected Result:* > Just suggestion, screen should scroll to the top where the decision tree resides when drag toward to the decision tree, or the split the model and decision tree to two different section with different scroll bar. > *Justification:* > Having more than 20 properties/attributes under a model such as applicant / customer is common in the banking section for rule check. Even the decision tree is not officially released, everything works fantastic except this critical feature which prevent us from using it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2638) Enumerations drop quotes when double quotes are used

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-2638?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-2638: ------------------------------------ Assignee: Toni Rikkola (was: Michael Anstis) > Enumerations drop quotes when double quotes are used > ---------------------------------------------------- > > Key: DROOLS-2638 > URL: https://issues.redhat.com/browse/DROOLS-2638 > Project: Drools > Issue Type: Bug > Components: Enumerations Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > > https://github.com/kiegroup/kie-wb-common/pull/1890 > @Rikkola The issue reported in the JIRA seem to be resolved; however I noticed (given an enumeration defined as Person.name: ['a', '"b, c"', 'd']) that the generated DRL is Person( name == "b, c" ) whereas should it be Person( name == "\"b, c\"" )? Closing and re-opening the decision table keeps the correct values selected in the table. I also tried defining the BRL fragment to use a literal value for the enumeration and this gave the same results (DRL possibly incorrect, but re-opening and editing the column was OK). > I also checked Guided Rules and the DRL is equally wrong however re-opening the rule also led to the wrong enumeration value being selected in the editor (it selected the first option by default) and the DRL showing the same (i.e. I set it to "b, c" and re-opening the file selected a). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2630) Guided Decision Tables: Not possible to use comma in 'is contained in' when using BRL

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-2630?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-2630: ------------------------------------ Assignee: Toni Rikkola (was: Michael Anstis) > Guided Decision Tables: Not possible to use comma in 'is contained in' when using BRL > ------------------------------------------------------------------------------------- > > Key: DROOLS-2630 > URL: https://issues.redhat.com/browse/DROOLS-2630 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2288) Guided Rule Editor: Not possible to reopen FROM ACCUMULATE

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-2288?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-2288: ------------------------------------ Assignee: Toni Rikkola (was: Michael Anstis) > Guided Rule Editor: Not possible to reopen FROM ACCUMULATE > ---------------------------------------------------------- > > Key: DROOLS-2288 > URL: https://issues.redhat.com/browse/DROOLS-2288 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Attachments: GuidedComplex.png > > > Create the rule in the image and when you reopen the rule an error about "FROM ACCUMULATE" appears. > !GuidedComplex.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13188) Exception while exporting metrics during WildFly initialization

by Mads Opheim (Jira)

[ https://issues.redhat.com/browse/WFLY-13188?page=com.atlassian.jira.plugi... ] Mads Opheim commented on WFLY-13188: ------------------------------------ Can confirm that we also get this issue, running Wildfly 18 (on OpenShift, if that matters), scraped by Prometheus. > Exception while exporting metrics during WildFly initialization > --------------------------------------------------------------- > > Key: WFLY-13188 > URL: https://issues.redhat.com/browse/WFLY-13188 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Affects Versions: 18.0.1.Final, 19.0.0.Beta2 > Reporter: Ehsan Zaery Moghaddam > Assignee: Brian Stansberry > Priority: Major > Labels: Microprofile > > When the open tracing system is enabled and some metrics are exposed, if when the WildFly is in the startup process, the Prometheus server calls the /metrics endpoint, WildFly prints a stacktrace for each metrics that is has detected (i.e. more than thousands) with the following message: > *WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available > * > In some cases the error persists, even after the server startup is done and we need to restart the WildFly; but we couldn't find the exact scenario for that. > Here is an example for wildfly_jpa_second_level_cache_size_in_memory metric: > {code} > 2020-03-02 09:38:06,739 WARN [management I/O-2] [metrics] Unable to export metric wildfly_jpa_second_level_cache_size_in_memory: java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute second-level-cache-size-in-memory on [ > ("deployment" => "application.ear"), > ("subdeployment" => "application-persistence.jar"), > ("subsystem" => "jpa"), > ("hibernate-persistence-unit" => "application.ear/application-persistence.jar#app"), > ("entity-cache" => "com.app.persistence.entity.Country") > ]: "WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available". > at org.wildfly.extension.microprofile.metrics.MetricCollector.readAttributeValue(MetricCollector.java:303) > at org.wildfly.extension.microprofile.metrics.MetricCollector.access$200(MetricCollector.java:70) > at org.wildfly.extension.microprofile.metrics.MetricCollector$2.getValue(MetricCollector.java:174) > at org.wildfly.extension.microprofile.metrics.MetricCollector$2.getValue(MetricCollector.java:171) > at io.smallrye.metrics.exporters.OpenMetricsExporter.createSimpleValueLine(OpenMetricsExporter.java:445) > at io.smallrye.metrics.exporters.OpenMetricsExporter.exposeEntries(OpenMetricsExporter.java:178) > at io.smallrye.metrics.exporters.OpenMetricsExporter.getEntriesForScope(OpenMetricsExporter.java:150) > at io.smallrye.metrics.exporters.OpenMetricsExporter.exportAllScopes(OpenMetricsExporter.java:101) > at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:116) > at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:73) > at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.handleRequest(MetricsContextService.java:81) > at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51) > at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35) > at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91) > at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211) > at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92) > at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78) > at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49) > at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57) > at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75) > at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:666) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376) > at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255) > at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136) > at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:59) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 July 2020