Bug 1335084
| Summary: | Retrieving ACC when daemon mode is used | ||
|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Richard Bourner <rbourner> |
| Component: | OptaPlanner | Assignee: | Geoffrey De Smet <gdesmet> |
| Status: | CLOSED EOL | QA Contact: | Lukáš Petrovický <lpetrovi> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.0 | CC: | rbourner |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-27 19:13:12 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I've fixed this on master for 7.0, but I've also renamed ACC to "score calculation speed" there (something we can't do in the 6.x series) because of a decision made after a IRC #optaplanner-dev discussion. https://github.com/droolsjbpm/optaplanner/commit/7c170573f2add6be67475ba4536f12a8e9428b9a If we get all acks for 6.x, it's possible to only backport the ACC rendering, but it turns out that it's not simple to do so. Is it worth the effort? Geoffrey De Smet <ge0ffrey.spam> updated the status of jira PLANNER-578 to Resolved |
Description of problem: When using Planner in daemon mode, the solver doesn't return, even when a termination is set. For this reason, we cannot get some of the runtime information such as the ACC which is contained in the following log statement: "Solving ended: time spent ({}), best score ({}), average calculate count per second ({}),"+ " environment mode ({}) even when the solver does not end?" Since the ACC is useful information, it would be nice to be able to get it, even if the solver doesn't return. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: