Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-1836

SolverManager: Unable to terminateEarly() or close() a problem when it is in the state of SOLVING_SCHEDULED

XMLWordPrintable

    • 2020 Week 07-09 (from Feb 10)
    • 3
    • Hide
      • Let SloverManager solve more problems than ParallelSolverCount, so that some of the problems are scheduled.
      • Call terminateEarly() on them and check their status afterward.

      Don't forget to wait for a bit in order to let the threads terminate successfully before checking their status. Currently, they will not do so and will be kept in the SOLVING_SCHEDULED state, even though they should have changed their status to NOT_SOLVING.

      Show
      Let SloverManager solve more problems than ParallelSolverCount, so that some of the problems are scheduled. Call terminateEarly() on them and check their status afterward. Don't forget to wait for a bit in order to let the threads terminate successfully before checking their status. Currently, they will not do so and will be kept in the SOLVING_SCHEDULED state, even though they should have changed their status to NOT_SOLVING.
    • NEW
    • NEW

      Methods terminateEarly() and close() are not able to terminate problems in a SOLVING_SCHEDULED status.

      See the following PR for a reproducible: https://github.com/kiegroup/optaplanner/pull/661

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              mtomco Michal TomĨo (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: