[jboss-jira] [JBoss JIRA] Commented: (JBRULES-3146) timer rule cannot work fine, if the method 'ksession.fireAllRules()' is called before we reload KnowlegeSession.

Mark Proctor (JIRA) jira-events at lists.jboss.org
Tue Aug 9 10:39:24 EDT 2011


    [ https://issues.jboss.org/browse/JBRULES-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619675#comment-12619675 ] 

Mark Proctor commented on JBRULES-3146:
---------------------------------------

I'm now working on this. It's going to take a fair bit of work. As there are only persistence mechanisms for the jBPM timer. The idea is to take the jBPM timer persistence mechanism and centralise it for all timers to work.

> timer rule cannot work fine, if the method 'ksession.fireAllRules()' is called before we reload KnowlegeSession.
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-3146
>                 URL: https://issues.jboss.org/browse/JBRULES-3146
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core
>    Affects Versions: 5.2.0.Final
>            Reporter: winton xu
>            Assignee: Mark Proctor
>            Priority: Critical
>         Attachments: TimerAndCalendarTest.java.txt
>
>
> we can reproduce it by following steps.
> 1. create a knowledge session. and call the method 'fireAllRules()'
> 2. reload knowledge session.
> 3. crate and build a timer rule.
> 4. fire the timer rule.
> [Actual Result]
> the timer rule cannot work fine.
> [Expected Result]
> the timer rule can work fine.
> (please check the attachement 'TimerAndCalendarTest.java.txt')

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

        


More information about the jboss-jira mailing list