February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5043) ConcurrentModificationException thrown from org.drools.modelcompiler.constraints.LambdaAccumulator.hashCode

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5043?page=com.atlassian.jira.plug... ] Luca Molteni resolved DROOLS-5043. ---------------------------------- Resolution: Done > ConcurrentModificationException thrown from org.drools.modelcompiler.constraints.LambdaAccumulator.hashCode > ----------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5043 > URL: https://issues.redhat.com/browse/DROOLS-5043 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.33.0.Final > Reporter: Radovan Synek > Assignee: Luca Molteni > Priority: Critical > Attachments: stacktrace > > > CME is thrown from org.drools.modelcompiler.constraints.LambdaAccumulator.hashCode in OptaPlanner KIE Server extension tests. One of the failing tests is for example [1]. > The executable model is switched on because the test creates SolverFactory from KieContainer [2], that is already compiler via a kie-maven-plugin - see the corresponding testing KJAR [3]. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [3] https://github.com/kiegroup/droolsjbpm-integration/tree/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1937) Release WildFly Elytron 1.10.5.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1937: ------------------------------------- Summary: Release WildFly Elytron 1.10.5.Final Key: ELY-1937 URL: https://issues.redhat.com/browse/ELY-1937 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.10.5.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5077) Prepare Openshift summit demo for Mario-Daniele-Edo

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5077?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-5077: --------------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) > Prepare Openshift summit demo for Mario-Daniele-Edo > --------------------------------------------------- > > Key: DROOLS-5077 > URL: https://issues.redhat.com/browse/DROOLS-5077 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1936) Backport new MicroProifle JWT module

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1936: ------------------------------------- Summary: Backport new MicroProifle JWT module Key: ELY-1936 URL: https://issues.redhat.com/browse/ELY-1936 Project: WildFly Elytron Issue Type: Bug Components: MicroProfile Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.10.5.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5077) Prepare Openshift summit demo for Mario-Daniele-Edo

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-5077: ------------------------------------------ Summary: Prepare Openshift summit demo for Mario-Daniele-Edo Key: DROOLS-5077 URL: https://issues.redhat.com/browse/DROOLS-5077 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5075) [DMN Designer] properties panel is not refreshed for top level output header

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5075?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-5075. ------------------------------- Resolution: Duplicate Issue > [DMN Designer] properties panel is not refreshed for top level output header > ---------------------------------------------------------------------------- > > Key: DROOLS-5075 > URL: https://issues.redhat.com/browse/DROOLS-5075 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Minor > Labels: drools-tools > > The issue was found during RHDM-1181 review, however it is probably not related. > The DMN Decision table expression can have complex output - structure/context. In such case output header cells are in two levels. The issue is if the top level output header cell is selected, the properties panel is not refreshed. It is an issue if previously was selected for example input header cell, then after selection change, an inappropriate information is shown in the properties panel. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5075) [DMN Designer] properties panel is not refreshed for top level output header

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5075?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-5075: ------------------------------------- Will be resolved as part of DROOLS-5060 > [DMN Designer] properties panel is not refreshed for top level output header > ---------------------------------------------------------------------------- > > Key: DROOLS-5075 > URL: https://issues.redhat.com/browse/DROOLS-5075 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Minor > Labels: drools-tools > > The issue was found during RHDM-1181 review, however it is probably not related. > The DMN Decision table expression can have complex output - structure/context. In such case output header cells are in two levels. The issue is if the top level output header cell is selected, the properties panel is not refreshed. It is an issue if previously was selected for example input header cell, then after selection change, an inappropriate information is shown in the properties panel. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10388) Persistent EJB timer timed_object_id naming discrepancy

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFLY-10388?page=com.atlassian.jira.plugi... ] Lukas Vydra commented on WFLY-10388: ------------------------------------ Hi, I'm not able to reproduce this behaviour, are you still able to reproduce it? If so, could you please provide us with more detailed reprosteps, configuration, etc. ? Thank you > Persistent EJB timer timed_object_id naming discrepancy > ------------------------------------------------------- > > Key: WFLY-10388 > URL: https://issues.redhat.com/browse/WFLY-10388 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 12.0.0.Final > Reporter: Boris Pran > Assignee: Lukas Vydra > Priority: Major > > Persistent EJB timers created declaratively (with @Schedule) create timed_object_id without version information while timers created using TimerService API include version info from deployment unit. > This way after version upgrade @Schedule timers survive but TimerService API created ones are lost and need to be created again. > I also seems that old timers remain created or at least their definitions can be seen in jboss_ejb_timer table. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1068) Automate AuthPolicy https://github.com/kiali/kiali/pull/2224

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1068?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1068. ----------------------------------- Assignee: Hayk Hovsepyan Resolution: Done > Automate AuthPolicy https://github.com/kiali/kiali/pull/2224 > ------------------------------------------------------------ > > Key: SWSQE-1068 > URL: https://issues.redhat.com/browse/SWSQE-1068 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5076) Rule compilation fails with date constraints on nested fact types

by Matteo Casalino (Jira)

Matteo Casalino created DROOLS-5076: --------------------------------------- Summary: Rule compilation fails with date constraints on nested fact types Key: DROOLS-5076 URL: https://issues.redhat.com/browse/DROOLS-5076 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.33.0.Final, 7.32.0.Final Reporter: Matteo Casalino Assignee: Mario Fusco Attachments: nested-date-constraint.tgz As of Drools 7.32.0.Final, patterns containing constraints on nested dates won't compile. For instance, given the following drl: {noformat} declare Fact n : Nested end declare Nested d : java.util.Date end rule "with nested date" when Fact(n!.d >= "01-Jan-2020", n!.d <= "10-Jan-2020") then end {noformat} we get the following error: Message [id=1, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 text=Unable to Analyse Expression n.d >= "01-Jan-2020": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] [Near : {... n.d >= "01-Jan-2020" ....}] ^] Message [id=2, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 text=Unable to Analyse Expression n.d <= "10-Jan-2020": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] [Near : {... n.d <= "10-Jan-2020" ....}] ^] {noformat} We don't reproduce with Drools <= 7.31.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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