September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2763) Heap Space Pile Up after some Time

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2763?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2763: -------------------------------- Security Sensitive Issue: (was: This issue is security relevant) > Heap Space Pile Up after some Time > ---------------------------------- > > Key: DROOLS-2763 > URL: https://issues.jboss.org/browse/DROOLS-2763 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 6.1.0.Final > Reporter: Bishnu Shankar Pandey > Assignee: Mario Fusco > Attachments: Rule Engine Heap ScreenShoot.png > > > After running rule Engine for 2-3 hours with data every 2 milliseconds I am getting heap space Error. After doing heap dump analysis i found that org.drools.core.phreak.RightTupleEntry.{next} class is taking 3.84GB heap space. Space and class details are in the below screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1958) [DMN Editor] Support use of imported data-types

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1958?page=com.atlassian.jira.plugi... ] Michael Anstis reopened DROOLS-1958: ------------------------------------ Re-opening as the DMN Specification relates to import of models and re-use of their elements (including, but not necessarily related to {{Decision}}, {{BusinessKnowledgeModel}}, {{InputData}}, {{KnowledgeSource}}, {{TextAnnotation}}, {{ItemDefinition}} etc). > [DMN Editor] Support use of imported data-types > ----------------------------------------------- > > Key: DROOLS-1958 > URL: https://issues.jboss.org/browse/DROOLS-1958 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: reported-by-qe > > "Support use of 'imported' data-types". DMN supports referencing other DMN files and importing types from that into the diagram being authored. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1398) Use Maven for compiling the workbench projects

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1398?page=com.atlassian.jira.plugi... ] Toni Rikkola resolved DROOLS-1398. ---------------------------------- Resolution: Out of Date This actually happened, but the tracking was done in other tickets. > Use Maven for compiling the workbench projects > ---------------------------------------------- > > Key: DROOLS-1398 > URL: https://issues.jboss.org/browse/DROOLS-1398 > Project: Drools > Issue Type: Feature Request > Reporter: Toni Rikkola > Assignee: Mario Fusco > > We currently use the kie-maven-plugin internally to compile the kjar's and only use Maven to provide the information about parent projects and dependencies for the project. > Yet we have the power of Maven underneath and we do not use it. It is impossible to use simple features like ignoring folders or moving code. Or more complicated, for example if you have your own rule asset format and need a Maven plugin to generate the DRL out of it. > However it is possible to set this functionality up. This causes problems: > * Same git tag built in the workbench produce different results depending on the Workbench version that is being used. This means that if you want to rebuild a lost kjar, you need to install the same workbench version that was originally used to create the first one > * Projects build in command line/build server can produce different kjars than the ones built with the workbench > Benefits we gain for going full Maven: > * Build the same artifacts anywhere > * Make Maven build cycle usable > * Make Maven plugins usable > * Run tests with any test tooling, users are not limited to Test Scenarios > What to keep in mind: > * If we let the user set the KIE version for the kie-maven-plugin. The internal compiler still uses the version the workbench has. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2983) Failed to checkout droolsjbpm-integration project on Windows

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2983?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2983. --------------------------------- Resolution: Rejected The maximum path length limitation can be easily resolved, see https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file#max... > Failed to checkout droolsjbpm-integration project on Windows > ------------------------------------------------------------ > > Key: DROOLS-2983 > URL: https://issues.jboss.org/browse/DROOLS-2983 > Project: Drools > Issue Type: Bug > Affects Versions: 7.12.0.Final > Environment: Windows 10 Enterprise > C:\ drive with NTFS filesystem > GIT version "git version 2.18.0.windows.1" > Reporter: Ramūnas K > Assignee: Mario Fusco > Priority: Critical > Attachments: screen_2018-09-10_14_03_11.png > > > Unable to checkout [droolsjbpm-integration|https://github.com/kiegroup/droolsjbpm-integration] on Windows 10 with NTFS file system. Filename {{kie-integration-test-coverage/kie-maven-plugin-separate-model-tests/kjar-with-separate-instrumentation-wrapper/src/test/resources/kjar-with-separate-instrumentation/src/main/resources/org/kie/integration/testcoverage/instrumentation}} is too long -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2983) Failed to checkout droolsjbpm-integration project on Windows

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2983?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2983: -------------------------------- Sprint: 2018 Week 36-38 > Failed to checkout droolsjbpm-integration project on Windows > ------------------------------------------------------------ > > Key: DROOLS-2983 > URL: https://issues.jboss.org/browse/DROOLS-2983 > Project: Drools > Issue Type: Bug > Affects Versions: 7.12.0.Final > Environment: Windows 10 Enterprise > C:\ drive with NTFS filesystem > GIT version "git version 2.18.0.windows.1" > Reporter: Ramūnas K > Assignee: Mario Fusco > Priority: Critical > Attachments: screen_2018-09-10_14_03_11.png > > > Unable to checkout [droolsjbpm-integration|https://github.com/kiegroup/droolsjbpm-integration] on Windows 10 with NTFS file system. Filename {{kie-integration-test-coverage/kie-maven-plugin-separate-model-tests/kjar-with-separate-instrumentation-wrapper/src/test/resources/kjar-with-separate-instrumentation/src/main/resources/org/kie/integration/testcoverage/instrumentation}} is too long -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2572) [DMN Editor] Graph View - Add support for using Java data-types

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2572?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2572: ----------------------------------- Priority: Minor (was: Major) > [DMN Editor] Graph View - Add support for using Java data-types > --------------------------------------------------------------- > > Key: DROOLS-2572 > URL: https://issues.jboss.org/browse/DROOLS-2572 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > Decision, BKM and InputData can have an "output data-type" selected. > Add support for selecting Java data types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1962) [DMN Editor] Decision service

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1962?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-1962: ----------------------------------- Priority: Critical (was: Major) > [DMN Editor] Decision service > ----------------------------- > > Key: DROOLS-1962 > URL: https://issues.jboss.org/browse/DROOLS-1962 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > > "In DRD it is rounded rectangle that surrounds all of the encapsulated decisions in the service. The inputs to the service are defined by all of the information requirements leading into the rounded rectangle. The outputs of the service are the decisions shown above the straight line bisecting the rounded rectangle. If there is no such line, all encapsulated decisions are exposed in the service output." cited form DMN Method and Style, Chapter 3, Decision Requirements -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1962) [DMN Editor] Decision service

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1962?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-1962: ----------------------------------- Issue Type: Feature Request (was: Task) Priority: Major (was: Trivial) > [DMN Editor] Decision service > ----------------------------- > > Key: DROOLS-1962 > URL: https://issues.jboss.org/browse/DROOLS-1962 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > > "In DRD it is rounded rectangle that surrounds all of the encapsulated decisions in the service. The inputs to the service are defined by all of the information requirements leading into the rounded rectangle. The outputs of the service are the decisions shown above the straight line bisecting the rounded rectangle. If there is no such line, all encapsulated decisions are exposed in the service output." cited form DMN Method and Style, Chapter 3, Decision Requirements -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2952) Hierarhical DataSource

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2952?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2952: -------------------------------- Sprint: 2018 Week 39-41 > Hierarhical DataSource > ---------------------- > > Key: DROOLS-2952 > URL: https://issues.jboss.org/browse/DROOLS-2952 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > > A really useful addition to DataSources would be scoped hierarchy. > Lets say I make DataSource d1, and unit u1 is instantiated with it. > I then want to instantiate d2, where d1 is the parent. I then instantiate u2 with d2. > That means u2 can seemlessly see and react to all the data in d2 and d1. u1 can only see and react to u1. > If u2 does inserts, those go into d2. > If u2 is garbage collected and no references remain on d2, it is also GC'd. This allows a for temporary and local DataSources, scoped to a given unit. > We can then add control structure methods such as: > moveAllToParent() > This would move all the FHs in d2 into d1. We might do this if u2 successfully finishes and d2 is about to be discarded, but we want to keep the results. > For a given DataSuorce we should be able to determine if it's root, or get it's level. We should always be able to get and insert into root, parent, or any numerically specific level. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2968) Improve stateless ksession throughput performance

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2968?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2968: -------------------------------- Sprint: 2018 Week 39-41 > Improve stateless ksession throughput performance > ------------------------------------------------- > > Key: DROOLS-2968 > URL: https://issues.jboss.org/browse/DROOLS-2968 > Project: Drools > Issue Type: Feature Request > Reporter: Mark Proctor > Assignee: Mario Fusco > Labels: MDP_BRAINFARTS > > Stateless access has become too heavy. We should look at streamlining the api, to avoid unnecessary work, and unnecessary (on demand) object creation. For example we know if rules need timers, avoid the timer creation if not necessary. > Also we should look at (with evaluation first) to determine if a Three local cache of ksessions, with reset, will help improve GC impact. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 September 2018