[jboss-jira] [JBoss JIRA] Updated: (JBRULES-2749) Various rules stop firing when adding more, totally unrelated rules to a knowledge base

[Mark Proctor (JIRA)]

     [ https://issues.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Proctor updated JBRULES-2749:
----------------------------------

    Fix Version/s: 5.2.0.CR1
         Assignee: Geoffrey De Smet  (was: Mark Proctor)


geoffrey: can you verify if this is still broken and distill it down to a minimal unit test for edson and I to fix.

> Various rules stop firing when adding more, totally unrelated rules to a knowledge base
> ---------------------------------------------------------------------------------------
>
>                 Key: JBRULES-2749
>                 URL: https://issues.jboss.org/browse/JBRULES-2749
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-compiler (expert), drools-core  (expert)
>    Affects Versions: 5.1.1.FINAL
>         Environment: Environment 1: Fedora Core 12 x86_64, Sun JVM 1.6.0_20 64-bit Server VM
> Environment 2: Windows XP Professional, Service Pack 3, 32 bit; Sun JVM 1.6.0_20 32-bit Server VM
>            Reporter: Ansgar Konermann
>            Assignee: Geoffrey De Smet
>             Fix For: 5.2.0.CR1
>
>         Attachments: drools-boundary-tests.git.ZIP
>
>
> A certain rule suddenly stops firing when adding more and more rules to the knowledge base, which (not only?) on first sight have *nothing* to do with the rule in question.
> We created a few unit tests which show the faulty behaviour.
> What we observed so far:
> * when using declared functions plus declared data types, this error occurrs.
> * sometimes, one can work around this problem by renaming a package. We're not sure if this is a reliable workaround, i. e. works in all situations.
> * one can work around this problem by not using declared functions. We're not sure if this is a reliable workaround.
> Find attached a ZIPed git repository containing:
> * a Maven 2.1+ pom.xml suitable to trigger the unit tests via mvn test
> * Java source files for a TestNG-based unit test
> * example drools source files to illustrate the problem (used by the unit tests)
> Please have a look at java file RuleDoesNotFireIfUsingDeclaredFunctionAndTooManyPackages.java. This should make quite clear what we're expecting of the drools library and where it fails to fulfil these expectations.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira