May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4000) Highlight of cells with issue is lost when one cell is fixed

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4000?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4000: -------------------------------- Attachment: highlight.webm > Highlight of cells with issue is lost when one cell is fixed > ------------------------------------------------------------ > > Key: DROOLS-4000 > URL: https://issues.jboss.org/browse/DROOLS-4000 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: ScenarioSimulation > Attachments: highlight.webm > > > Aim of this ticket: > - Improve error messages sent by server to the cell popover in case of specific errors: eg. > [~kkufova]: I noticed that Impossible to parse as boolean message keeps getting displayed instead of an actual help. For example, I used falsee instead of false. I think in this case we definitely need The expected value is 'false' but the actual one is 'falsee'. Another scenario: if the expected value is null but I enter [] instead, the error message is Error with this value: Impossible to parse as boolean. It doesn't say anything about the actual value being null. > - Improving exceptions handling related to this part: at the moment, any type of exception could be sent to the popover (eg. OutOfMemory). Only a subset should be managed. > Related to https://issues.jboss.org/browse/DROOLS-3838 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4000) Improving error messages from backend to cell popover

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4000: ----------------------------------- Summary: Improving error messages from backend to cell popover Key: DROOLS-4000 URL: https://issues.jboss.org/browse/DROOLS-4000 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Affects Versions: 7.22.0.Final Reporter: Jozef Marko Assignee: Yeser Amer Aim of this ticket: - Improve error messages sent by server to the cell popover in case of specific errors: eg. [~kkufova]: I noticed that Impossible to parse as boolean message keeps getting displayed instead of an actual help. For example, I used falsee instead of false. I think in this case we definitely need The expected value is 'false' but the actual one is 'falsee'. Another scenario: if the expected value is null but I enter [] instead, the error message is Error with this value: Impossible to parse as boolean. It doesn't say anything about the actual value being null. - Improving exceptions handling related to this part: at the moment, any type of exception could be sent to the popover (eg. OutOfMemory). Only a subset should be managed. Related to https://issues.jboss.org/browse/DROOLS-3838 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3999) Profile and improve performances for DMN executor

by Mario Fusco (Jira)

Mario Fusco created DROOLS-3999: ----------------------------------- Summary: Profile and improve performances for DMN executor Key: DROOLS-3999 URL: https://issues.jboss.org/browse/DROOLS-3999 Project: Drools Issue Type: Enhancement Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3998) DMN FEEL parser Table61 error with aliased type

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3998: -------------------------------------- Summary: DMN FEEL parser Table61 error with aliased type Key: DROOLS-3998 URL: https://issues.jboss.org/browse/DROOLS-3998 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3991) java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader

by Anuradha Prabhala (Jira)

[ https://issues.jboss.org/browse/DROOLS-3991?page=com.atlassian.jira.plugi... ] Anuradha Prabhala resolved DROOLS-3991. --------------------------------------- Resolution: Done > java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3991 > URL: https://issues.jboss.org/browse/DROOLS-3991 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.15.0.Final > Reporter: Anuradha Prabhala > Assignee: Maciej Swiderski > Priority: Critical > > I deployed 2 war files in wildfly 14. Both of them are drools projects that are trying to execute some rules. The problem is that only one of the war file is able to execute drools rule. The other fails with the below Internal Server Error: > Caused by: java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader > at org.drools.compiler.kie.builder.impl.KieServicesImpl.getKieClasspathContainer(KieServicesImpl.java:107) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.getKieClasspathContainer(KieServicesImpl.java:79) > at org.drools.examples.helloworld.HelloWorldExample.drools(HelloWorldExample.java:49) > at com.sample.rest.MessageRestService.Testdrools(MessageRestService.java:26) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3991) java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader

by Anuradha Prabhala (Jira)

[ https://issues.jboss.org/browse/DROOLS-3991?page=com.atlassian.jira.plugi... ] Anuradha Prabhala closed DROOLS-3991. ------------------------------------- > java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3991 > URL: https://issues.jboss.org/browse/DROOLS-3991 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.15.0.Final > Reporter: Anuradha Prabhala > Assignee: Maciej Swiderski > Priority: Critical > > I deployed 2 war files in wildfly 14. Both of them are drools projects that are trying to execute some rules. The problem is that only one of the war file is able to execute drools rule. The other fails with the below Internal Server Error: > Caused by: java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader > at org.drools.compiler.kie.builder.impl.KieServicesImpl.getKieClasspathContainer(KieServicesImpl.java:107) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.getKieClasspathContainer(KieServicesImpl.java:79) > at org.drools.examples.helloworld.HelloWorldExample.drools(HelloWorldExample.java:49) > at com.sample.rest.MessageRestService.Testdrools(MessageRestService.java:26) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3991) java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader

by Anuradha Prabhala (Jira)

[ https://issues.jboss.org/browse/DROOLS-3991?page=com.atlassian.jira.plugi... ] Anuradha Prabhala commented on DROOLS-3991: ------------------------------------------- I found out that in my wildfly standalone.xml, drools was a global module.. Hence common jars were present under /wildfly/modules. Hence these common jars are not allowing parallel modules to execute drools rules, as coomon jars always create 1 Kie Container. Fix to the problem: Removed global module in standalone.xml and respective applications started using their own drools jars to create Kie Containers which then solved the issue. > java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3991 > URL: https://issues.jboss.org/browse/DROOLS-3991 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.15.0.Final > Reporter: Anuradha Prabhala > Assignee: Maciej Swiderski > Priority: Critical > > I deployed 2 war files in wildfly 14. Both of them are drools projects that are trying to execute some rules. The problem is that only one of the war file is able to execute drools rule. The other fails with the below Internal Server Error: > Caused by: java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader > at org.drools.compiler.kie.builder.impl.KieServicesImpl.getKieClasspathContainer(KieServicesImpl.java:107) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.getKieClasspathContainer(KieServicesImpl.java:79) > at org.drools.examples.helloworld.HelloWorldExample.drools(HelloWorldExample.java:49) > at com.sample.rest.MessageRestService.Testdrools(MessageRestService.java:26) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-160) Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed

by Romain Pelisse (Jira)

[ https://issues.jboss.org/browse/REMJMX-160?page=com.atlassian.jira.plugin... ] Romain Pelisse reassigned REMJMX-160: ------------------------------------- Assignee: JBoss SET (was: Darran Lofthouse) > Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed > -------------------------------------------------------------------------------------- > > Key: REMJMX-160 > URL: https://issues.jboss.org/browse/REMJMX-160 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 1.1.3.Final, 3.0.1.Final > Reporter: Masafumi Miura > Assignee: JBoss SET > Priority: Major > Attachments: Memory.png, leaks.png > > > In JMX client application, every JMXConnectorFactory#connect() invocation creates a new ThreadGroup which is never reclaimed. > https://github.com/jbossas/remoting-jmx/blob/3.0.1.Final/src/main/java/or... > If a JMX client application lives for long periods of time and repeats to invoke JMXConnectorFactory#connect() and JMXConnector#close(), a lot of ThreadGroup instances are retained eventually. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3720) [DMN Designer] Included Models - Set the data types count in the IncludedModel entity

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3720?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3720: -------------------------------- Description: When a model is imported, set the data types count in the {{IncludedModel}} entity. h3. Acceptance criteria - Zero data types count (/) - Non Zero data types count (/) - Data Types count updated in the original model (/) was: When a model is imported, set the data types count in the {{IncludedModel}} entity. h3. Acceptance criteria - Zero data types count (/) - Non Zero data types count - Data Types count updated in the original model > [DMN Designer] Included Models - Set the data types count in the IncludedModel entity > ------------------------------------------------------------------------------------- > > Key: DROOLS-3720 > URL: https://issues.jboss.org/browse/DROOLS-3720 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > When a model is imported, set the data types count in the {{IncludedModel}} entity. > h3. Acceptance criteria > - Zero data types count (/) > - Non Zero data types count (/) > - Data Types count updated in the original model (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3721) [DMN Designer] Included Models - Set the DRG elements count in the IncludedModel entity

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3721?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3721: -------------------------------- Description: When a model is imported, set the DRG elements count in the {{IncludedModel}} entity. h3. Acceptance criteria - Zero elements count (/) - Non Zero elements count (/) - Elements count updated in the original model (/) was: When a model is imported, set the DRG elements count in the {{IncludedModel}} entity. h3. Acceptance criteria - Zero elements count (/) - Non Zero elements count - Elements count updated in the original model > [DMN Designer] Included Models - Set the DRG elements count in the IncludedModel entity > --------------------------------------------------------------------------------------- > > Key: DROOLS-3721 > URL: https://issues.jboss.org/browse/DROOLS-3721 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > When a model is imported, set the DRG elements count in the {{IncludedModel}} entity. > h3. Acceptance criteria > - Zero elements count (/) > - Non Zero elements count (/) > - Elements count updated in the original model (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 May 2019