[JBoss JIRA] (DROOLS-5050) Issue with alpha node and expired events rule execution
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5050?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5050:
---------------------------------
Sprint: 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10))
> Issue with alpha node and expired events rule execution
> -------------------------------------------------------
>
> Key: DROOLS-5050
> URL: https://issues.redhat.com/browse/DROOLS-5050
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.33.0.Final
> Reporter: Marcell Pessanha Cruz
> Assignee: Luca Molteni
> Priority: Critical
>
> Alpha node based rules evaluated for expired events are not all executed during the inference cycle.
> With the following rules:
> {noformat}
> declare DummyEvent
> @role( event )
> @timestamp( eventTimestamp )
> @expires( 1s )
> end
> rule R1
> when
> $evt : DummyEvent()
> then
> end
> rule R2
> when
> $evt : ApplicationEvent()
> then
> end
> {noformat}
> and this code to execute:
> {noformat}
> public interface ApplicationEvent { }
> public static class DummyEvent implements ApplicationEvent {...}
> /* .... */
> final KieSession kieSession = kieBase.newKieSession( sessionConfig, null );
> PseudoClockScheduler clock = kieSession.getSessionClock();
> final long currentTime = clock.getCurrentTime();
> clock.advanceTime(10, TimeUnit.SECONDS);
> kieSession.insert(new DummyEvent(10, currentTime));
> kieSession.fireAllRules()
> {noformat}
> then only the *R1* rule is executed, not R2.
> Note: the same test case passes on 7.2.0.Final and earlier versions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4891) Further Optimize Lambdas in Executable Model
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-4891?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-4891:
---------------------------------
Sprint: 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10))
> Further Optimize Lambdas in Executable Model
> --------------------------------------------
>
> Key: DROOLS-4891
> URL: https://issues.redhat.com/browse/DROOLS-4891
> Project: Drools
> Issue Type: Enhancement
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
> Labels: good-first-issue
>
> Lambda shouldn't be externalized depending on the variable name but on the actual lambda.
> So
> person.name == a
> person.name == b
> Is effectively the same lambda and should externalized once.
> Hint: we could rename the parameters to p1, p2, p3, promote the types to fully qualified names and get this result.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5025) Wrong BitMask created by a complex setter argument in modify block
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5025?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5025:
---------------------------------
Sprint: 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10))
> Wrong BitMask created by a complex setter argument in modify block
> ------------------------------------------------------------------
>
> Key: DROOLS-5025
> URL: https://issues.redhat.com/browse/DROOLS-5025
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.32.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Luca Molteni
> Priority: Major
> Labels: good-first-issue
>
> With a complex setter argument in modify block like this:
> {noformat}
> import org.drools.modelcompiler.domain.Person;
> rule R
> when
> $p: Person(address.street == "street1")
> then
> modify($p) { setLikes( String.valueOf(($p.getAddress().getStreet() + $p.getAddress().getCity()))) };
> end
> {noformat}
> executable model creates BitMask for "likes" and "address" thus causes a wrong property reactivity behavior.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5101) rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5101?page=com.atlassian.jira.plug... ]
Toni Rikkola commented on DROOLS-5101:
--------------------------------------
Hi [~charles.herrick] it looks like you are having several issues with RHDM. The use of RHDM hints me that you are a paying customer or work for a company that bought support from Red Hat. I recommend you report these issues directly to Red Hat support so they can help you with proper settings or raising up bugs and getting them fixed. It is not wrong to directly report tickets to this DROOLS Jira, but I'm just letting you know are entitled to a better service.
> rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError
> --------------------------------------------------------------------------
>
> Key: DROOLS-5101
> URL: https://issues.redhat.com/browse/DROOLS-5101
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.26.0.Final
> Reporter: Charles Herrick
> Assignee: Toni Rikkola
> Priority: Critical
>
> 09:13:02,818 ERROR [org.kie.workbench.common.services.backend.builder.core.Builder] (default task-95) GC overhead limit exceeded: java.lang.OutOfMemoryError: GC overhead limit exceeded
> 09:13:05,335 ERROR [stderr] (default task-95) java.lang.OutOfMemoryError: GC overhead limit exceeded
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5114) Hacep on Openshift 4.3 with Drools 7.34.0-SNAPSHOT error on startup
by Massimiliano Dessi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5114?page=com.atlassian.jira.plug... ]
Massimiliano Dessi resolved DROOLS-5114.
----------------------------------------
Resolution: Won't Fix
With a empty maven repo the issue was present, with a fresh crc instance the problem disappears, this means something cached for days in the docker repo
> Hacep on Openshift 4.3 with Drools 7.34.0-SNAPSHOT error on startup
> -------------------------------------------------------------------
>
> Key: DROOLS-5114
> URL: https://issues.redhat.com/browse/DROOLS-5114
> Project: Drools
> Issue Type: Bug
> Reporter: Massimiliano Dessi
> Assignee: Massimiliano Dessi
> Priority: Major
>
> Dockerfile use java-1.8.0-openjdk-headless the project is build using open jdk 1.8 but at the pod startup the following stacktrace is printed in the log and prevent the pod to start correctly
> java.lang.UnsupportedClassVersionError: org/drools/cep/Rule_StockAverage302521058AccumulateExpression0Invoker has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:757)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.internalDefineClass(JavaDialectRuntimeData.java:617)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.fastFindClass(JavaDialectRuntimeData.java:588)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.loadClass(JavaDialectRuntimeData.java:565)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
> at org.drools.core.rule.JavaDialectRuntimeData.wire(JavaDialectRuntimeData.java:459)
> at org.drools.core.rule.JavaDialectRuntimeData.wire(JavaDialectRuntimeData.java:450)
> at org.drools.core.rule.JavaDialectRuntimeData.wireAll(JavaDialectRuntimeData.java:280)
> at org.drools.core.rule.JavaDialectRuntimeData.onBeforeExecute(JavaDialectRuntimeData.java:252)
> at org.drools.core.rule.DialectRuntimeRegistry.onBeforeExecute(DialectRuntimeRegistry.java:137)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.reloadAll(KnowledgeBuilderImpl.java:1448)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.wireAllRules(KnowledgeBuilderImpl.java:927)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildRules(KnowledgeBuilderImpl.java:2504)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildPackages(KnowledgeBuilderImpl.java:2428)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:106)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:98)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:261)
> at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:195)
> at org.drools.compiler.kie.builder.impl.AbstractKieModule.createKieBase(AbstractKieModule.java:209)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:407)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:375)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBaseFromKieSessionModel(KieContainerImpl.java:560)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:536)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:459)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:442)
> at org.kie.hacep.consumer.DroolsConsumerHandler.createAndInitializeSessionContextWithoutSnapshot(DroolsConsumerHandler.java:89)
> at org.kie.hacep.consumer.DroolsConsumerHandler.initializeKieSessionContext(DroolsConsumerHandler.java:69)
> at org.kie.hacep.consumer.DroolsConsumerHandler.<init>(DroolsConsumerHandler.java:57)
> at org.kie.hacep.core.infra.consumer.ConsumerController.<init>(ConsumerController.java:33)
> at org.kie.hacep.core.Bootstrap.startConsumers(Bootstrap.java:102)
> at org.kie.hacep.core.Bootstrap.startEngine(Bootstrap.java:47)
> at org.kie.hacep.endpoint.bootstrap.BootstrapListener.initServices(BootstrapListener.java:37)
> at org.kie.hacep.endpoint.bootstrap.BootstrapListener.contextInitialized(BootstrapListener.java:33)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4683)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5146)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5118) DMN "time offset" property wrongly erroring
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-5118:
--------------------------------------
Summary: DMN "time offset" property wrongly erroring
Key: DROOLS-5118
URL: https://issues.redhat.com/browse/DROOLS-5118
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
Accessing an empty component of a time/date time object.
Current impl. returnin null. This is correct.
Current impl. also reporting an Error. This is not correct.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5117) DMN built-in FEEL function median with empty list
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-5117:
--------------------------------------
Summary: DMN built-in FEEL function median with empty list
Key: DROOLS-5117
URL: https://issues.redhat.com/browse/DROOLS-5117
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
current impl: FEEL ERROR while evaluating literal expression 'median([])': The parameter 'list', in function median(), cannot be empty.
spec example Table 69: Semantics of list functions
bq. median( [ ] ) = null
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months