| Summary: | When multithreaded evaluation is enabled the application never stops | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Tomas Schlosser <tschloss> | ||||
| Component: | BRE (Expert, Fusion) | Assignee: | Nobody <nobody> | ||||
| Status: | VERIFIED --- | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | BRMS 5.3.0.GA | CC: | lpetrovi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | BRMS 5.3.0.GA | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
I am not sure about what to do with this one. The documentation states [1] that "it is an experimental feature", but the fact is that due to some changes we did in 5.2/5.3 it no longer works. In 5.1 it worked, but without the benefits we expected. I don't want to completely remove the code, as we will probably fix this and put to good use when we implement support for multiple agendas, but at the moment, this feature should not be used. Do we change the documentation to clearly state that? Do we generate a compilation error if someone tries to use it? Please let me know what you think. Thanks [1] http://docs.jboss.org/drools/release/5.4.0.Beta1/drools-fusion-docs/html_single/index.html#d0e1198 (In reply to comment #2) > Do we change the documentation to clearly state that? Do we generate a > compilation error if someone tries to use it? I'd suggest throwing some exception / emitting a warning. The exception is probably a better idea, as it will force current users of the option to re-consider Code changed to raise an exception if the user tries to set the multithread evaluation option to YES/TRUE. Javadoc changed to make the option deprecated. Documentation changed to warn the option is not supported. Yes, the exception is raised. Disabling testing with multithreaded evaluation. |
Created attachment 529775 [details] Simple test class Description of problem: Some threads must hang somewhere as long as at least one operation is done with the session (fact inserted, one rule fired, query evaluated,...). Version-Release number of selected component (if applicable): BRMS-5.2.0.GA How reproducible: Every time. Steps to Reproduce: 1. run included class Actual results: The application hangs and is never finished. Expected results: The application prints 'Hello world!' and 'I'm finished...' and ends. Additional info: