December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3928) DMN refactor codegen for same strategy

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-3928?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-3928: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18)) > DMN refactor codegen for same strategy > -------------------------------------- > > Key: DROOLS-3928 > URL: https://issues.redhat.com/browse/DROOLS-3928 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4724) [DMN Designer] Do not default to a LiteralExpression when no expression is defined

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4724?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4724: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9) (was: 2019 Week 47-49 (from Nov 18)) > [DMN Designer] Do not default to a LiteralExpression when no expression is defined > ---------------------------------------------------------------------------------- > > Key: DROOLS-4724 > URL: https://issues.redhat.com/browse/DROOLS-4724 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-11-29 12-04-18.png, error.log, image-2019-11-04-19-39-01-113.png, image-2019-11-04-19-40-27-201.png, m.dmn, save-context.webm, screenshot-1.png, screenshot-2.png > > > Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. > However Error message is reported anyway to the user: > !image-2019-11-04-19-39-01-113.png|thumbnail! > This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression > !image-2019-11-04-19-40-27-201.png|thumbnail! > so the current behavior is not consistent across re-open of the editor. > Let's revert this default. > The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. > Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). > Currently, the DMN Compiler will throw 1 Warning. > Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). > Currently, the DMN Validator schema check is not reporting any XSD violation. > h2. Manual acceptance test > Try to save default / empty > h3. Business Central > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation > h3. Kogito > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4774) Investigate executable model performances on large rule sets

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4774?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4774: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9) (was: 2019 Week 47-49 (from Nov 18)) > Investigate executable model performances on large rule sets > ------------------------------------------------------------ > > Key: DROOLS-4774 > URL: https://issues.redhat.com/browse/DROOLS-4774 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4645) High memory consumption with JIT

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4645?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4645: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18)) > High memory consumption with JIT > -------------------------------- > > Key: DROOLS-4645 > URL: https://issues.redhat.com/browse/DROOLS-4645 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.29.0.Final > Reporter: Radovan Synek > Assignee: Mario Fusco > Priority: Critical > Attachments: Screenshot from 2019-10-15 10-30-27.png, Screenshot from 2019-10-15 10-31-53.png > > > Employee Rostering example for OptaPlanner shows excessive memory consumption, which is connected with Drools score calculation. > Please see the reproducer - running it without drools JIT finishes on time with 3GB of memory while with drools JIT being active it fails due to "GC overhead limit exceeded" despite the fact it god twice as much memory. > Logging (add -Dlogback.level.org.optaplanner=trace to the execute_jit.sh script) showed there is a huge pillar move changing ~hundreds of entities which takes seconds to calculate score. During this move's evaluation, the memory consumption increases to a point when GC takes over and later fails. > Memory sampling and heap dump investigation showed there are ~10^7 objects of org.drools.core.reteoo.FromNodeLeftTuple class, taking more memory than any other data type in the VM. > See the attached screenshots. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4858) Avoid materialized nested lambdas of method called "execute"

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4858: ------------------------------------ Summary: Avoid materialized nested lambdas of method called "execute" Key: DROOLS-4858 URL: https://issues.redhat.com/browse/DROOLS-4858 Project: Drools Issue Type: Bug Components: executable model Reporter: Luca Molteni Assignee: Luca Molteni Fix For: 7.3.1.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4817) Raise the timeout for generated tests

by Daniel Rosa (Jira)

[ https://issues.redhat.com/browse/DROOLS-4817?page=com.atlassian.jira.plug... ] Daniel Rosa updated DROOLS-4817: -------------------------------- Sprint: (was: 2019 Week 47-49 (from Nov 18)) > Raise the timeout for generated tests > ------------------------------------- > > Key: DROOLS-4817 > URL: https://issues.redhat.com/browse/DROOLS-4817 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the generated tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4817) Raise the timeout for generated tests

by Daniel Rosa (Jira)

[ https://issues.redhat.com/browse/DROOLS-4817?page=com.atlassian.jira.plug... ] Daniel Rosa updated DROOLS-4817: -------------------------------- Sprint: 2019 Week 47-49 (from Nov 18) > Raise the timeout for generated tests > ------------------------------------- > > Key: DROOLS-4817 > URL: https://issues.redhat.com/browse/DROOLS-4817 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the generated tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-280) Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFWIP-280?page=com.atlassian.jira.plugin... ] Jan Kasik updated WFWIP-280: ---------------------------- Description: Warning which are propagated to log from {noformat}io.smallrye.jwt.auth{noformat} package don't have assigned logging ID. Example: {code} 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token {code} was: Warning which are propagated to log from `io.smallrye.jwt.auth` package don't have assigned logging ID. Example: {code} 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token {code} > Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID > ---------------------------------------------------------------------- > > Key: WFWIP-280 > URL: https://issues.redhat.com/browse/WFWIP-280 > Project: WildFly WIP > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Major > > Warning which are propagated to log from {noformat}io.smallrye.jwt.auth{noformat} package don't have assigned logging ID. > Example: > {code} > 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-280) Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFWIP-280?page=com.atlassian.jira.plugin... ] Jan Kasik updated WFWIP-280: ---------------------------- Description: Warning which are propagated to log from io.smallrye.jwt.auth package don't have assigned logging ID. Example: {code} 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token {code} was: Warning which are propagated to log from {noformat}io.smallrye.jwt.auth{noformat} package don't have assigned logging ID. Example: {code} 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token {code} > Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID > ---------------------------------------------------------------------- > > Key: WFWIP-280 > URL: https://issues.redhat.com/browse/WFWIP-280 > Project: WildFly WIP > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Major > > Warning which are propagated to log from io.smallrye.jwt.auth package don't have assigned logging ID. > Example: > {code} > 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-280) Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID

by Jan Kasik (Jira)

Jan Kasik created WFWIP-280: ------------------------------- Summary: Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID Key: WFWIP-280 URL: https://issues.redhat.com/browse/WFWIP-280 Project: WildFly WIP Issue Type: Bug Components: MP JWT Reporter: Jan Kasik Assignee: Darran Lofthouse Warning which are propagated to log from `io.smallrye.jwt.auth` package don't have assigned logging ID. Example: {code} 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token {code} -- 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 December 2019