[jboss-jira] [JBoss JIRA] (DROOLS-272) KieSession.fireUntilHalt() consumes 100% CPU

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on DROOLS-272:
------------------------------------------------

Ryan Zhang <rzhang at redhat.com> changed the Status of [bug 1012140|https://bugzilla.redhat.com/show_bug.cgi?id=1012140] from MODIFIED to ON_QA
                
> KieSession.fireUntilHalt() consumes 100% CPU
> --------------------------------------------
>
>                 Key: DROOLS-272
>                 URL: https://issues.jboss.org/browse/DROOLS-272
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions:  6.0.0.CR3
>         Environment: Mac OS-X 1.8.5 + Hotspot JDK 1.7.0_40, RHEL 6.4 + OpenJDK 1.7.0_25, Fedora 18 + Java 6.
>            Reporter: Duncan Doyle
>            Assignee: Edson Tirelli
>            Priority: Blocker
>             Fix For: 6.0.0.CR5
>
>
> When I run a KieSession.fireUntilHalt(), my application starts consuming 100% CPU, without anything actually happening inside the app (no events/facts are being inserted, no rules are activated/fired, etc.). We've tested this on multiple machines, different OSs, different JDKs, etc., and they all show the same behaviour.
> I've created a small test that shows the problem. The test loads a simple DRL via KieClasspathContainer, retrieves a new KieSession and runs a KieSession.fireUntilHalt() in a separate thread. After launching the thread, I let the main thread sleep for 30 seconds (3 * 10) and during this time period, CPU load increases to 100%. I then halt the session and sleep for another 10 seconds, which causes the CPU load to back to normal. The test project can be found here: https://github.com/DuncanDoyle/DroolsFireUntilHalt/
> Just run 'mvn clean test' on the project.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira