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

[JBoss JIRA] (AS7-4672) cache-type...

[JBoss JIRA] Created:...

Ansgar Konermann (JIRA)

Friday, 22 October 2010 Fri, 22 Oct '10

9:31 a.m.

Various rules stop firing when adding more, totally unrelated rules to a knowledge base --------------------------------------------------------------------------------------- Key: JBRULES-2749 URL: https://jira.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: Mark Proctor 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. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Ansgar Konermann (JIRA)

Friday, 22 October Fri, 22 Oct

9:33 a.m.

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

[ https://jira.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plugin... ] Ansgar Konermann updated JBRULES-2749: -------------------------------------- Attachment: drools-boundary-tests.git.ZIP Added unit tests to show erroneous behaviour.

...

Various rules stop firing when adding more, totally unrelated rules to a knowledge base --------------------------------------------------------------------------------------- Key: JBRULES-2749 URL: https://jira.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: Mark Proctor 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. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Mark Proctor (JIRA)

Tuesday, 17 May Tue, 17 May

10:36 p.m.

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

[ https://issues.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plug... ] 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

Geoffrey De Smet (JIRA)

Thursday, 19 May Thu, 19 May

6:32 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared

[ https://issues.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plug... ] Geoffrey De Smet updated JBRULES-2749: -------------------------------------- Summary: Various rules stop firing when they are in unlucky packagename and there is a function declared (was: Various rules stop firing when adding more, totally unrelated rules to a knowledge base)

...

Various rules stop firing when they are in unlucky packagename and there is a function declared ----------------------------------------------------------------------------------------------- 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

Geoffrey De Smet (JIRA)

6:36 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

[ https://issues.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plug... ] Geoffrey De Smet updated JBRULES-2749: -------------------------------------- Summary: Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared (was: Various rules stop firing when they are in unlucky packagename and there is a function declared)

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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

Geoffrey De Smet (JIRA)

6:53 a.m.

New subject: [JBoss JIRA] Assigned: (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

[ https://issues.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plug... ] Geoffrey De Smet reassigned JBRULES-2749: ----------------------------------------- Assignee: Mark Proctor (was: Geoffrey De Smet)

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor 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

Geoffrey De Smet (JIRA)

6:53 a.m.

New subject: [JBoss JIRA] Commented: (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

[ https://issues.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-2749: ------------------------------------------- Issue is still present on master. I 've pushed an ignored test on MiscTest that replicates the issue (distilled from the attachment): {code} @Test @Ignore("TODO unignore when fixing JBRULES-2749") public void testPackageNameOfTheBeast() throws Exception { {code}

...

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

Geoffrey De Smet (JIRA)

Thursday, 26 May Thu, 26 May

2:36 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.2.0.CR2 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

Geoffrey De Smet (JIRA)

Thursday, 23 June Thu, 23 Jun

1 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.3.0.Beta1 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

Geoffrey De Smet (JIRA)

Tuesday, 9 August Tue, 9 Aug

6:41 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.3.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

Geoffrey De Smet (JIRA)

Sunday, 25 September Sun, 25 Sep

3:04 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.3.0.Final 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

Geoffrey De Smet (Updated) (JIRA)

Friday, 21 October Fri, 21 Oct

10:02 a.m.

New subject: [JBoss JIRA] (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.4.0.Beta1 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. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (Updated) (JIRA)

Tuesday, 20 December Tue, 20 Dec

4:15 a.m.

New subject: [JBoss JIRA] (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.4.0.Beta2 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.

Geoffrey De Smet (JIRA)

Wednesday, 1 February Wed, 1 Feb

4:26 a.m.

New subject: [JBoss JIRA] (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.4.0.Beta3 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.

Toni Rikkola (JIRA)

Thursday, 12 April Thu, 12 Apr

2:37 a.m.

New subject: [JBoss JIRA] (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

[ https://issues.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plug... ] Toni Rikkola updated JBRULES-2749: ---------------------------------- Fix Version/s: 5.4.0.Final (was: 5.4.0.CR1)

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.4.0.Final 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.

Mark Proctor (JIRA)

Sunday, 29 April Sun, 29 Apr

12:32 a.m.

New subject: [JBoss JIRA] (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

[ https://issues.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plug... ] Mark Proctor resolved JBRULES-2749. ----------------------------------- Resolution: Done This doesn't seem to be broken any more, athough I don't know when the specific fix was applied. However the test is now there with @Ignore removed. Please improve teh test if problems persist.

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.4.0.Final 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.

Mark Proctor (JIRA)

3:17 a.m.

New subject: [JBoss JIRA] (JBRULES-2749) Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

[ https://issues.jboss.org/browse/JBRULES-2749?page=com.atlassian.jira.plug... ] Mark Proctor closed JBRULES-2749. ---------------------------------

...

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared ------------------------------------------------------------------------------------------------------------------------ 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: Mark Proctor Fix For: 5.4.0.Final 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.

4637

days inactive

5192

days old

jboss-jira@lists.jboss.org

Manage subscription

16 comments

5 participants

tags (0)

participants (5)

Ansgar Konermann (JIRA)
Geoffrey De Smet (JIRA)
Geoffrey De Smet (Updated) (JIRA)
Mark Proctor (JIRA)
Toni Rikkola (JIRA)

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

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