August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-276) Stream mode with CR4-Pre1 generates rules looping

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-276?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-276: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1012933|https://bugzilla.redhat.com/show_bug.cgi?id=1012933] from VERIFIED to CLOSED > Stream mode with CR4-Pre1 generates rules looping > -------------------------------------------------- > > Key: DROOLS-276 > URL: https://issues.jboss.org/browse/DROOLS-276 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Environment: Drools 6.0.0.CR4-Pre1 > Reporter: Richard Bourner > Assignee: Mario Fusco > Priority: Blocker > Fix For: 6.0.0.CR5 > > Attachments: Drools6Stream.zip > > > When in STREAM mode, our rules are looping because of an update. > The attached example doesn't demonstrate the looping but one rule is fired twice where it should only fire once. We are supposing that the issue is the same. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-352) JUSTIFIED status is overridden to STATED when TMS is enabled for superclass

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-352?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-352: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1034277|https://bugzilla.redhat.com/show_bug.cgi?id=1034277] from VERIFIED to CLOSED > JUSTIFIED status is overridden to STATED when TMS is enabled for superclass > --------------------------------------------------------------------------- > > Key: DROOLS-352 > URL: https://issues.jboss.org/browse/DROOLS-352 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 5.5.1.Final, 6.1.0.Beta1 > > > Enabling TMS for a class initializes the Equality Key (as STATED - otherwise the TMS would have been enabled before) for all instances of that class. > This behavior, however, overrides the Key of any instance of a subclass which has a dedicated OTN, on which the TMS has been enabled -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-280) lock-on-active broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-280?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-280: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1025824|https://bugzilla.redhat.com/show_bug.cgi?id=1025824] from VERIFIED to CLOSED > lock-on-active broken > --------------------- > > Key: DROOLS-280 > URL: https://issues.jboss.org/browse/DROOLS-280 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Reporter: Anthony Patricio > Assignee: Mario Fusco > Fix For: 6.0.0.Final > > > Hi, > lock-on-active is not working as expected. > I seems to work as activation-group. > Works fine with 5.x > Fails with 6.0.0 CR3 and CR4 > Fact: > {code:java} > public class Poc implements Serializable { > private static final long serialVersionUID = 1L; > private long id = 1; > private boolean test1 = false; > private boolean test2 = false; > private int foundTest = 0; > ... > } > {code} > Rule: > {code:java} > rule "test1" > lock-on-active > dialect "mvel" > when > $poc:Poc( isTest1() ) > then > System.out.println("test1 found"); > modify($poc) { setFoundTest($poc.getFoundTest() + 1) } > end > rule "test2" > lock-on-active > dialect "mvel" > when > $poc:Poc( isTest2() ) > then > System.out.println("test2 found"); > modify($poc) { setFoundTest($poc.getFoundTest() + 1) } > end > {code} > Test: > {code:java} > @Test > public void lockOnActiveTest() { > // Get the Knowledge base from the DRL file > KieSession kSession = getSF(); > > Poc poc = new Poc(); > poc.setTest1(true); > poc.setTest2(true); > > kSession.insert(poc); > > // Fire the rules > kSession.fireAllRules(); > > assertTrue("broken",poc.getFoundTest()==2); > > // Clean up > kSession.dispose(); > } > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-346) Phreak broke the Audit View

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-346?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-346: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1032252|https://bugzilla.redhat.com/show_bug.cgi?id=1032252] from VERIFIED to CLOSED > Phreak broke the Audit View > --------------------------- > > Key: DROOLS-346 > URL: https://issues.jboss.org/browse/DROOLS-346 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-372) InstantiationError during condition evaluation in Drools 6.0.0.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-372?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-372: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1040007|https://bugzilla.redhat.com/show_bug.cgi?id=1040007] from VERIFIED to CLOSED > InstantiationError during condition evaluation in Drools 6.0.0.Final > -------------------------------------------------------------------- > > Key: DROOLS-372 > URL: https://issues.jboss.org/browse/DROOLS-372 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Environment: reproduced on both jdk 6 and jdk 7 > Reporter: Loic Albertin > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > Attachments: drools-issue.zip > > > Kindly find bellow the initial discussion from rules-user(a)list.jboss.org > In addition I attach a sample project that reproduce the error. > To run it simply type 'mvn clean install exec:java'. > An interesting thing is that on my environment the issue always appears at the 21st insertion. > {quote} > Hi all, > I'm migrating from an old Drools 5.1 version to 6.0.0.Final. Sometimes (I don't really get under which conditions as sometimes it works), I'm facing an InstantiationError exception when I insert a fact into a stateful kie session. This exception is thrown by a generated class named ConditionEvaluator<UUID> which doesn't help for debugging! > The inserted object is a basic POJO (named JasmineEventEB) except for an attribute named "value" which accept any "Serializable" object and which is causing the issue. > The rule condition is quite simple > $e : JasmineEventEB(probe == "Button:pris" && value == "1") > In debugging I found that it failed when evaluating the value == "1" part. I can also confirm that the value for the actually inserted JasmineEventEB is a string. > The stacktrace is: > {noformat} > java.lang.InstantiationError: java.io.Serializable > at ConditionEvaluatorae1a73837e8146bda23004a0450e2e52.evaluate(Unknown Source) > at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:212) > at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:169) > at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:134) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:502) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:387) > at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:138) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:502) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:377) > at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:288) > at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:260) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:360) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:279) > at org.drools.core.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1149) > at org.drools.core.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1093) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:308) > {noformat} > I tested both with the java and mvel dialect with the same result. > Does someone has already encountered this kind of error? > If you need more details or clarifications please let me know. > Thanks & regards, > Loïc > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-336) Property Reactivity fails on phreak

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-336?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-336: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1029071|https://bugzilla.redhat.com/show_bug.cgi?id=1029071] from VERIFIED to CLOSED > Property Reactivity fails on phreak > ----------------------------------- > > Key: DROOLS-336 > URL: https://issues.jboss.org/browse/DROOLS-336 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > In LeftInputAdapterNode a modifyByPass happens, for a sink that has not been reached before. So it thinks it's new, and thus propagates as an insert > The real bug comes in doInsertObject method. It creates a child LT here, even though once it enters doInsertSegmentMemory the mask intersect fails. This leaves a child LT, that is not propagated. Next time update is called, as the LT is there it thinks it's a modify and propagates as a modify - but it never reached the beta node or the LeftMemory, and thus the memory corruption. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-292) Current AgendaGroup does not give way when setFocus is called

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-292?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-292: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1016727|https://bugzilla.redhat.com/show_bug.cgi?id=1016727] from VERIFIED to CLOSED > Current AgendaGroup does not give way when setFocus is called > ------------------------------------------------------------- > > Key: DROOLS-292 > URL: https://issues.jboss.org/browse/DROOLS-292 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.0.0.CR5 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-266) KIE resolving dependend artifacts issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-266?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-266: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1014157|https://bugzilla.redhat.com/show_bug.cgi?id=1014157] from VERIFIED to CLOSED > KIE resolving dependend artifacts issue > --------------------------------------- > > Key: DROOLS-266 > URL: https://issues.jboss.org/browse/DROOLS-266 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR3 > Reporter: Kurt Stam > Assignee: Mario Fusco > Fix For: 6.0.0.CR5 > > Attachments: kie-load-from-maven-issue.tgz, kie-load-from-maven-issue.tgz > > > This happens when for a dependency the scope is > - set to 'provided' and > - a parameter (in the case ${jbpm.version}) is used in the version field. > So the relevant entry in the pom is: > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-core</artifactId> > <version>${drools.version}</version> > <scope>provided</scope> > </dependency> > which leads to > 11:15:02,584 WARN Dependency artifact not found for: org.jbpm:jbpm-bpmn2:${jbpm.version} > and then the NPE. I'm guessing the parameter is not being resolved. > 1. it probably should resolve parameters > 2. if a dependency is scoped as 'provided' I think it is supposed to locate it on the classpath and NOT from maven. However I'm not sure this is the way that works in testing anyway. > 3. if the dependency cannot be found it should probably stop and not even proceed rather then warn? > 4. it should be interesting to see why it gets the NPE. > If you change the dependency from 'provided' to 'test' things work fine. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-361) Incremental compilation requires to provide the list of modified files even if not necessary

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-361?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-361: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1036807|https://bugzilla.redhat.com/show_bug.cgi?id=1036807] from VERIFIED to CLOSED > Incremental compilation requires to provide the list of modified files even if not necessary > -------------------------------------------------------------------------------------------- > > Key: DROOLS-361 > URL: https://issues.jboss.org/browse/DROOLS-361 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > Incremental compilation requires to provide the list of the modified files since the last compilation. However this could be error-prone and violates the DRY principle, because this list could be automatically calculated. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-169) Evaluator 'str' does not work wit logical or

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-169?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-169: ------------------------------------------------ Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 971282|https://bugzilla.redhat.com/show_bug.cgi?id=971282] from VERIFIED to CLOSED > Evaluator 'str' does not work wit logical or > -------------------------------------------- > > Key: DROOLS-169 > URL: https://issues.jboss.org/browse/DROOLS-169 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.0.Beta4 > > > The str custom evaluator when used in conjuction of other constraints connected with logical or, like in the following example: > {code} > RoutingMessage( routingValue == "R2" || routingValue str[startsWith] "R1" ) > {code} > throws a ClassCastException when evaluated. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2014