[rules-users] Bugs in Drools 5.3.0 break Fusion event processing

[Edson Tirelli]

   Thanks Richard,

   I will fix them for the next release.

   Edson

2011/11/9 Richard Calmbach <rcalmbac at gmail.com>

> Edson: Thanks for the quick reply. I created these JIRA issues:
>
> F1: Duplicate job scheduling in
> org.drools.time.impl.DefaultTimerJobInstance.call()
> - https://issues.jboss.org/browse/JBRULES-3284
>
> F2: NullPointerException in
> org.drools.time.impl.DefaultTimerJobInstance.compareTo(DefaultTimerJobInstance)
> - https://issues.jboss.org/browse/JBRULES-3285
>
> F3: org.drools.time.TimerService.scheduleJob(Job, JobContext, Trigger)
> suddenly requires non-null JobContext
> - https://issues.jboss.org/browse/JBRULES-3286
>
> While you are working on the event scheduling system, you may also want to
> look at these two earlier bug reports for Drools 5.2.0:
>
> Long.MAX_VALUE duration for "A and not(B after A)" type rules causes
> invalid session clock time in rule RHS when running with pseudo clock
> - https://issues.jboss.org/browse/JBRULES-3100
>
> "A and not(B after A)" type rules don't fire when session clock has
> negative values (pre Unix epoch)
> - https://issues.jboss.org/browse/JBRULES-3103
>
> I have not checked their status in Drools 5.3.0, but the description
> should tell you whether they still apply.
>
> FWIW, among all of these, F2 (JBRULES-3285) has the highest priority (as
> it's breaking my unit tests), followed by F1 (JBRULES-3284). Thanks!
>
> Vincent: Yes, I think there is risk. Even if you don't use jobs
> explicitly, Drools uses the same event scheduling system for both internal
> events and application-defined events and jobs. The main problem is this:
> How do you establish correctness of your code and the overall system? Well,
> you make sure your unit tests and functional tests pass. As it stands, I
> cannot get my tests to pass with Drools 5.3.0, so I cannot put Drools 5.3.0
> in production. No matter which version you use, only good test coverage
> will give you the assurance that your system is functioning properly. I
> encourage you to try out Drools 5.3.0 (in a test environment) and to report
> any issues you run into. It can only help make Drools better.
>
> 2011/11/9 Vincent LEGENDRE <vincent.legendre at eurodecision.com>
>
>> Just wondering : does these problems happends because you use clocks and
>> jobs, or is it general to fusion 5.3 ?
>> Did not migrate my project on 5.3 for now.
>> So do you think there is a risk, knowing that I only use very basic
>> fusion features ?
>>
>> ------------------------------
>> *De: *"Edson Tirelli" <ed.tirelli at gmail.com>
>> *À: *"Rules Users List" <rules-users at lists.jboss.org>
>> *Envoyé: *Mercredi 9 Novembre 2011 14:53:00
>> *Objet: *Re: [rules-users] Bugs in Drools 5.3.0 break Fusion event
>> processing
>>
>>
>>
>>    Richard,
>>
>>    This is great info. Yes, please open JIRA's for all 3 issues and we
>> will make sure this is fixed for the next release.
>>
>>    Thank you,
>>    Edson
>>
>
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>


-- 
  Edson Tirelli
  JBoss Drools Core Development
  JBoss by Red Hat @ www.jboss.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20111110/e058189d/attachment.html