[jboss-jira] [JBoss JIRA] Closed: (JBRULES-1904) Event insert is causing near-100% CPU utilization
Edson Tirelli (JIRA)
jira-events at lists.jboss.org
Wed Dec 31 11:04:54 EST 2008
[ https://jira.jboss.org/jira/browse/JBRULES-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edson Tirelli closed JBRULES-1904.
----------------------------------
Fix Version/s: 5.0.0.M5
Resolution: Duplicate Issue
> Event insert is causing near-100% CPU utilization
> -------------------------------------------------
>
> Key: JBRULES-1904
> URL: https://jira.jboss.org/jira/browse/JBRULES-1904
> Project: JBoss Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-compiler
> Affects Versions: 5.0.0.M4
> Environment: Mac OS X 10.5.6/ Java 5_07; and Solaris 10, java 5 _15
> Reporter: Radim Marek
> Assignee: Edson Tirelli
> Fix For: 5.0.0.M5
>
> Attachments: bugreport.tar.gz
>
>
> An Event inserted into the stateful session is correctly processed, but starts near-100% CPU load. Logic implemented according to drools-compiler/src/test/java/org/drools/integrationtests/CepEspTest.java, but needs longer observation to notice CPU load. No rules necessary to demonstrate this.
> I'm going to attach maven project that demonstrates the problem within the test method testEventBasedCPULoad (please, ignore other two test methods - related to different bug).
> Profiling of the running session shows org.drools.common.AbstractWorkingMemory.executeQueuedActions() as the cause of the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list