[
https://jira.jboss.org/jira/browse/JBRULES-2145?page=com.atlassian.jira.p...
]
Geoffrey De Smet resolved JBRULES-2145.
---------------------------------------
Resolution: Out of Date
Assignee: Geoffrey De Smet (was: Edson Tirelli)
No longer occurs on the 5.1.0.M2-SNAPSHOT of today, so it's out of date.
I am switching drools-solver back to trunk :)
Trunk 5.1.0-snapshot hangs if pounded enough
--------------------------------------------
Key: JBRULES-2145
URL:
https://jira.jboss.org/jira/browse/JBRULES-2145
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.1.0.M1
Environment: quad core, ubuntu 9.04
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Critical
Fix For: 5.1.0.M2
To reproduce:
svn checkout <drools>
edit drools/drools-solver/pom.xml and comment out the dependencies on 5.0.1
(1) run PatientAdmissionScheduleApp in the working directory
drools/drools-solver/drools-solver-examples
Click load testdata01.xml
Click solve
In the output, you 'll see something like this:
Trunk is bugged 35/652
Trunk is bugged 36/652
Trunk is bugged 37/652
At some point it might hang before it reaches 652. It does not happen every time, so try
again it does reach 652.
I've seen it occur about 1 out of 3 times.
And if it hangs, it really hangs: all 4 of my CPU's are not buzy etc. Definitely a
race condition.
--
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