Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-404

ModClusterService stop commands are always draining sessions

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.3.0.Final, 1.2.8.Final
    • Fix Version/s: 1.2.9.Final, 1.3.1.Alpha1
    • Component/s: None
    • Labels:
      None

      Description

      Using the ModClusterService stop or stopContext commands via CLI always fails to move a context to the STOPPED state after failing to drain the active sessions. So these commands then aren't very useful for quickly stopping the context when desired if you can't do it without draining.

      I think it'd make sense for any draining done by manual stops to also follow the session draining strategy used by typical stops from undeploy events.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jfclere Jean-Frederic Clere
                Reporter:
                aogburn Aaron Ogburn
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: