[JBoss JIRA] (DROOLS-2409) Memory Leak in sliding window
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-2409?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-2409.
---------------------------------
Resolution: Won't Fix
> Memory Leak in sliding window
> -----------------------------
>
> Key: DROOLS-2409
> URL: https://issues.redhat.com/browse/DROOLS-2409
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 7.6.0.Final
> Environment: Mac with Java 1.8 using Spring Boot (see attached demo project)
> Reporter: Mike Baranski
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: complete.tar.gz
>
>
> See attached project.
> `gradle test` causes an out of memory exception on my machine after ~2.6 million events. Events should be released for GC after 1 second, but that does not appear to be happening.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-2148) not able to execute a drl file when packaged inside a jar file
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-2148?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-2148.
---------------------------------
Resolution: Cannot Reproduce
> not able to execute a drl file when packaged inside a jar file
> --------------------------------------------------------------
>
> Key: DROOLS-2148
> URL: https://issues.redhat.com/browse/DROOLS-2148
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.2.0.Final
> Reporter: Vardhaman Magadum
> Assignee: Mario Fusco
> Priority: Major
> Attachments: Jar Structure.png, Rule1.drl, eclipse project.png, projectStructure.png
>
>
> Hi all,
> I have created a simplest rule project in KIE workbench 7.2, After build and deploy i am able to download the jar for my project from the artifact repository. now i want to execute the rules from a java maven project. I have put the jar in the resources folder of the maven project, scanning the jar and trying to load all the rule artifacts in the kie base. but i am not able to execute the rules inside the drl file which is inside the jar file. I have attached the drl file, jar structure, eclipse project structure and debug in eclipse. please help, pls update if any further details required.
> Thanks
> Vardhaman
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-2348) KIE Workbench deployment on Tomcat fails when already droolsEngine jars are in tomcat/lib folder
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-2348?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-2348.
---------------------------------
Resolution: Out of Date
> KIE Workbench deployment on Tomcat fails when already droolsEngine jars are in tomcat/lib folder
> ------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2348
> URL: https://issues.redhat.com/browse/DROOLS-2348
> Project: Drools
> Issue Type: Bug
> Components: integration
> Affects Versions: 7.6.0.Final
> Reporter: Senthil Kumar Kamaraj
> Assignee: Mario Fusco
> Priority: Major
>
> Hi,
> We have deployed the drools engine and KIE workbench on Tomcat container.
> droolsEngine - All the jars from "drools-distribution-7.6.0.Final" are copied into the <tomcat_home>/lib folder
> KIE Workbench - kie-drools-wb-7.6.0.Final-tomcat8.war deployment on <tomcat_home>/webapps folder.
> Now the issue is, we are getting the below error, so that KIE Workbench is not deploying on tomcat.
> Caused by: java.lang.ClassCastException: org.drools.beliefs.bayes.assembler.BayesAssemblerService cannot be cast to org.kie.api.internal.assembler.KieAssemblerService
> If we exculde drools-beliefs-7.6.0.Final.jar jar from <tomcat_home>/lib folder then the KIE workbench is deployed successfully.
> But, both the deployments of drools 7.4.1 is succeeded without excluding drools-beliefs-7.4.1.Final.jar.
> Can any one help me in this issue..
> Is there any restriction to deploy both on a single container (tomcat).
> Thanks
> Senthil
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-1448) [XLS Decision Table] Integer values for Double attributes causes validation error
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-1448?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-1448.
---------------------------------
Resolution: Done
> [XLS Decision Table] Integer values for Double attributes causes validation error
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-1448
> URL: https://issues.redhat.com/browse/DROOLS-1448
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.0.0.Beta6
> Reporter: Jozef Marko
> Assignee: Mario Fusco
> Priority: Minor
> Labels: dtable_testday_preparation, qe-test-day, reported-by-qe
> Attachments: Driver.java, ExamplePolicyPricing.xls, Policy.java, Screenshot from 2017-02-02 10-22-21.png
>
>
> If the XLS decision contains Integer values for column ( attribute ) that is Double data type, then the XLS decision table is not validated successfully. After conversion to guided decision table is the table validated successfully.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-1579) Using salience with parallel agenda
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-1579?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-1579.
---------------------------------
Resolution: Won't Do
> Using salience with parallel agenda
> -----------------------------------
>
> Key: DROOLS-1579
> URL: https://issues.redhat.com/browse/DROOLS-1579
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 7.0.0.Final
> Reporter: Tibor Zimanyi
> Assignee: Mario Fusco
> Priority: Minor
> Labels: parallel-agenda
>
> Using salience with parallel agenda is probably not feasible, because salience is ordering of rules and ordering introduces rule serialization. However we should discuss this more so we know 100% that there are no feasible solutions.
> One possible scenario could be to put all salienced rules (and relatives according to rete) to separate partition, which is handled by separate agenda and process this agenda before all other agendas. In such case these "other" agendas could be processed in parallel after the "salienced" agenda is processed. Other name for this feature could be "postponed partitioning". First process everything that cannot be partitioned and then process everything that is partitioned in parallel.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-845) @KSession throws exception when using kmodule in separate jar
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-845?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-845:
-------------------------------
Sprint: 2019 Week 50-52 (from Dec 9)
> @KSession throws exception when using kmodule in separate jar
> -------------------------------------------------------------
>
> Key: DROOLS-845
> URL: https://issues.redhat.com/browse/DROOLS-845
> Project: Drools
> Issue Type: Bug
> Components: core engine, decision tables, kie server
> Affects Versions: 6.2.0.Final
> Environment: windows 7
> Reporter: lucio piccoli
> Assignee: Mario Fusco
> Priority: Major
> Attachments: drools-bug.zip
>
>
> i am using drools with a kmodules.xml and decisiontable inside a separate jar file. when i attempt to bind the @KSession to the spring application context it throws an nullpointer exception deep inside the annotation.
> org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'oft.onlineservice.business.FeeRulesEngineTest': Injection of kie dependencies failed; nested exception is java.lang.NullPointerException
> at org.kie.spring.annotations.AnnotationsPostProcessor.postProcessPropertyValues(AnnotationsPostProcessor.java:109)
> using a simple junittest shows the problem.
> public class FeeRulesEngineTest {
> @KSession( "ksession1")
> private StatelessKieSession ksession;
> @KBase("feeDecisionTable")
> private KieBase kbase;
> the kmodule.xml
> <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
> <kbase name="feeDecisionTable" packages="oft.rulesengine" default="true">
> <ksession name="ksession1" type="stateless" default="true" >
> </ksession>
> </kbase>
> </kmodule>
> the spring config is using the annonation postprocessor.
> <kie:import />
> <bean id="kiePostProcessor"
> class="org.kie.spring.annotations.KModuleAnnotationPostProcessor"/>
>
> my curent work around to is to use @Autowire for the KSession and KBase.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-1221) Add fail-safe and scalability functionality to the Drools (CEP) rules engine
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-1221?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-1221.
---------------------------------
Resolution: Out of Date
Implemented by HA CEP
> Add fail-safe and scalability functionality to the Drools (CEP) rules engine
> ----------------------------------------------------------------------------
>
> Key: DROOLS-1221
> URL: https://issues.redhat.com/browse/DROOLS-1221
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: Drools (CEP) Rule engine 6.4.0.Final
> Reporter: Tom Pijl
> Assignee: Mario Fusco
> Priority: Major
>
> The Drools Rule engine is currently not fail-safe and scalable which is a requirement for Cloud deployment.
> Add a possibility to persist the state of the working memory after each state change (perhaps linked to the fireAllRules()?) and related to that the possibility to restore the state in case of a crash (fail-safe requirement).
> This persistent state store can also be used to synchronize multiple engine instances (scalability requirement).
> Of course this has major impact on the performance of the engine, but it is the only way to make the engine useful in a multi-tenant Cloud environment
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months