[
http://jira.jboss.com/jira/browse/JBRULES-1152?page=comments#action_12375690 ]
Edson Tirelli commented on JBRULES-1152:
----------------------------------------
Michael, I don't think it is shadow facts related, but it is strange that the behavior
changed from 4.0.0 to 4.0.1.
Steve, if you can please provide us with a test case, we can dig and find out what is
happening.
One advise though: using dynamic beans as you are using is surely causing a performance
hit on you, because each rule consequence is setting more than one attribute. I mean,
dynamic beans will call update() automatically for each changed attribute, resulting in
unnecessary calls. Also, this may explain why setting power button pressed to false has a
better performance, since it is a boolean that is probably canceling a lot of activations
at once, while setting the state is not canceling that many activations and eventually
triggering a recursion.
You may want to take a look at using update() or using MVEL dialect modify call that will
trigger all changes at once.
my unit tests are hanging with drools 4.0.1
-------------------------------------------
Key: JBRULES-1152
URL:
http://jira.jboss.com/jira/browse/JBRULES-1152
Project: JBoss Rules
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.1
Environment: Java 1.5, Mac OX X 10.4.10, Drools 4.0.1
Reporter: Steve Miner
Assigned To: Mark Proctor
Sorry, I don't have very specific information. Some of my project's unit tests
are hanging with drools 4.0.1. No error, just not completing. I tried to debug a bit but
could not figure it out. Consider this an early warning until I can gather more info.
Everything worked fine with 4.0 so I went back to that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira