December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-4605) DMN alpha network

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4605?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4605: ----------------------------------- Sprint: 2020 Week 34-36 (from Aug 17), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30) (was: 2020 Week 34-36 (from Aug 17), 2020 Week 46-48 (from Nov 9)) > DMN alpha network > ----------------- > > Key: DROOLS-4605 > URL: https://issues.redhat.com/browse/DROOLS-4605 > Project: Drools > Issue Type: Story > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > > *Motivation*: a DMN decision table can be evaluated faster than naive algorithm by translating it into a Rete/Phreak, but the current kie7 approach is suffering from performance bottleneck artificially induced by use of kie7 rule units, which provide more harm than benefit to perfomance (performance is actually worst for most "realistic" cases). > *Goals*: a POC to understand what’s need to be done to support the alpha network compiler (wihout kie7 rule units) in DMN. We currently estimate it will take us 1 to 2 summer sprints and the output will be more epics to implement this feature. > *Impact*: alpha network compiler code refactors for the better use of. > One part of the POC was to hard-code the alpha network for a specific table ([DROOLS-4566]) the remained of the poc is to generalize the approach further to fully assess the impacts thanks to the poc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5202) Update bouncycastle to 1.67

by Boris Unckel (Jira)

Boris Unckel created WFCORE-5202: ------------------------------------ Summary: Update bouncycastle to 1.67 Key: WFCORE-5202 URL: https://issues.redhat.com/browse/WFCORE-5202 Project: WildFly Core Issue Type: Component Upgrade Components: Modules Affects Versions: 14.0.0.Beta2 Reporter: Boris Unckel Assignee: Richard Opalka Update to [Bouncycastle 1.67|https://mvnrepository.com/artifact/org.bouncycastle/bcprov-jdk15on/1.67]. [Releasenotes|https://bouncycastle.org/releasenotes.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5855) Update Drools MVN Archetype

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5855?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5855: ----------------------------------- Sprint: 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30) (was: 2020 Week 46-48 (from Nov 9)) > Update Drools MVN Archetype > --------------------------- > > Key: DROOLS-5855 > URL: https://issues.redhat.com/browse/DROOLS-5855 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > After the MVEL descoping it doesn't work anymore as it doesn't use drools-engine-classic but kieclasspathcontainer uses MVEL -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5808) XLS to GDST conversion should ensure types work

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5808?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5808: ----------------------------------- Sprint: 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30) (was: 2020 Week 46-48 (from Nov 9)) > XLS to GDST conversion should ensure types work > ----------------------------------------------- > > Key: DROOLS-5808 > URL: https://issues.redhat.com/browse/DROOLS-5808 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > BigDecimal, BigIntenger, long, float and double do not necessary work unless we add appropriate wrappers. Depends on the dialect that is used in the kbase, the current approach will default to Java dialect since that also works in MVEL. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5861) Include PMML trusty inside Kie-Server

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5861: ---------------------------------------- Summary: Include PMML trusty inside Kie-Server Key: DROOLS-5861 URL: https://issues.redhat.com/browse/DROOLS-5861 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Include PMML trusty inside Kie-Server (droolsjbpm-integration/kie-server-parent/) Look for PMML legacy references. See [ApplyPmmlModelCommandExecutor|https://github.com/kiegroup/droolsjbpm-know...] Verify Correct classloading/defaulting. Verify jpmml. For tests, see [README|https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie...] [KieServerDroolsIntegrationTest|https://github.com/kiegroup/droolsjbpm-int...] [DMNPMMLMiningIntegrationTest|https://github.com/kiegroup/droolsjbpm-integ...] Remember to compile/install modules before testing, since underlying Arquilian uses jars from m2 repo -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5742) Reduce the call to getServerInfo() in kie-server integration tests

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5742?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5742: ----------------------------------- Sprint: 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30) (was: 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9)) > Reduce the call to getServerInfo() in kie-server integration tests > ------------------------------------------------------------------ > > Key: DROOLS-5742 > URL: https://issues.redhat.com/browse/DROOLS-5742 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 7.45.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > getServerInfo() is called in integration tests 39 times (format x3 transport x2) = 234 times > It's called every time KieServicesClient is created (if config.getCapabilities() == null). > https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > So, we can suppress calling getServerInfo() by providing config.capabilities in test cases. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5870) DrlDumper does not generate the accumulate import

by Hiroko Miura (Jira)

[ https://issues.redhat.com/browse/DROOLS-5870?page=com.atlassian.jira.plug... ] Hiroko Miura commented on DROOLS-5870: -------------------------------------- Customer would like to know if there is any workaround on this issue. Please let me know if any. > DrlDumper does not generate the accumulate import > -------------------------------------------------- > > Key: DROOLS-5870 > URL: https://issues.redhat.com/browse/DROOLS-5870 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.44.0.Final, 7.46.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: import-accumulate-test.zip > > > DrlDumper is not printing out the accumulate import. > Here is an example code of PackageDescrBuilder. > {noformat} > PackageDescr packageDescr = DescrFactory.newPackage().name("examples.drools") > .newImport().target("java.math.BigDecimal").end() > .newAccumulateImport().target("examples.drools.accumulate.OriginalFunction").functionName("originalFunction").end() > .newRule().name("Test Rule") > .lhs() > .accumulate() > .source().pattern().type("TargetFact").id("$target", false) > .end() > .end() > .function("originalFunction", "$accumulateResult", false, "$target.hoge") > .constraint("true") > .end() > .end() > .rhs("System.out.println($accumulateResult);") > .end() > .end().getDescr(); > String drl = new DrlDumper().dump(packageDescr); > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14151) Introduce a base "health" subsystem and move microprofile-health to the microprofile feature-pack

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14151?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-14151: ------------------------------- Description: The microprofile-health-smallrye subsystem is provided by the wilfdfly galleon-pack. However its logical inclusion is in the microprofile feature pack (org.wildfly:wildfly-mp-feature-pack-galleon-common) which provides features for MicroProfile. We should move the subsystem (and extension) to this feature pack. However, the base WildFly server is still expected to provide "base" healthiness information (to determine when the application server is ready to serve requests) that can be consumed out of the box by a container platform such as Kubernetes. I propose to introduce a simple "health" subsystem (without any external dependencies) that provides a HTTP endpoints to probe the server healthiness. The microprofile-health-smallrye subsystem will be refactored to "plug" in the same HTTP endpoint and overrides the base health endpoint and provide the full features of MicroProfile health was: The microprofile-metrics-smallrye subsystem is provided by the wilfdfly galleon-pack. However its logical inclusion is in the microprofile feature pack (org.wildfly:wildfly-mp-feature-pack-galleon-common) which provides features for MicroProfile. We should move the subsystem (and extension) to this feature pack. However, the base WildFly server is still expected to provide "base" metrics (for the WildFly management model and the JVM) that can be consumed out of the box. I propose to introduce a simple "metrics" subsystem (without any external dependencies) that exposes the WildFly management model and the JVM (using JMX) to the /metrics endpoint (on the management port) with the Prometheus format. The microprofile-metrics-smallrye subsystem will be refactored to "plug" in the same HTTP endpoint and overrides the base metrics endpoint and provide the full features of MicroProfile metrics (application metrics, JSON output, etc.) > Introduce a base "health" subsystem and move microprofile-health to the microprofile feature-pack > ------------------------------------------------------------------------------------------------- > > Key: WFLY-14151 > URL: https://issues.redhat.com/browse/WFLY-14151 > Project: WildFly > Issue Type: Feature Request > Components: MP Metrics > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 22.0.0.Beta1 > > > The microprofile-health-smallrye subsystem is provided by the wilfdfly galleon-pack. > However its logical inclusion is in the microprofile feature pack (org.wildfly:wildfly-mp-feature-pack-galleon-common) which provides features for MicroProfile. > We should move the subsystem (and extension) to this feature pack. > However, the base WildFly server is still expected to provide "base" healthiness information (to determine when the application server is ready to serve requests) that can be consumed out of the box by a container platform such as Kubernetes. > I propose to introduce a simple "health" subsystem (without any external dependencies) that provides a HTTP endpoints to probe the server healthiness. > The microprofile-health-smallrye subsystem will be refactored to "plug" in the same HTTP endpoint and overrides the base health endpoint and provide the full features of MicroProfile health -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5200) Include the wildfly-openssl ppc64le binding

by Vladimir Dosoudil (Jira)

Vladimir Dosoudil created WFCORE-5200: ----------------------------------------- Summary: Include the wildfly-openssl ppc64le binding Key: WFCORE-5200 URL: https://issues.redhat.com/browse/WFCORE-5200 Project: WildFly Core Issue Type: Enhancement Components: Build System, Security Reporter: Vladimir Dosoudil Assignee: Darran Lofthouse The wildfly-openssl project source code include ppc64le bindings; we should include them. https://github.com/wildfly-security/wildfly-openssl-natives/tree/master/l... The code was there for a while (at least since 1.0.8 release) but it doesn't look like that variant was built and pushed to nexus: https://repository.jboss.org/org/wildfly/openssl/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-4291) Restore legacy (not "graceful") startup mode

by Jason Lee (Jira)

[ https://issues.redhat.com/browse/WFCORE-4291?page=com.atlassian.jira.plug... ] Jason Lee reassigned WFCORE-4291: --------------------------------- Assignee: Jason Lee (was: Brian Stansberry) > Restore legacy (not "graceful") startup mode > -------------------------------------------- > > Key: WFCORE-4291 > URL: https://issues.redhat.com/browse/WFCORE-4291 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Vladimir Grabarchuk > Assignee: Jason Lee > Priority: Major > > Please allow a configurable legacy startup mode which was the default before WF11, when components can service HTTP requests as soon as they are deployed, not when the container deploys all components. > The use case for this is the following: there is a configuration service component upon which other components depend for configuration data, requested and served via a HTTP request. With the new "graceful startup" this scenario no longer seems possible, as it results in read timeouts, mis-configured artifacts, and failed deployments altogether. > If generally feasible, another value of the *--start-mode=legacy* seems appropriate to accommodate the original (legacy) behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 December 2020