Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10821

mod_cluster stop/stop-context operations do not send STOP-* in when session draining was unsuccessful

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.ER2
    • 7.1.0.DR16, 7.1.0.DR17, 7.1.0.ER2
    • mod_cluster
    • None

    Description

      CLI operation description

      [standalone@localhost:9990 /] /subsystem=modcluster/:read-operation-description(name=stop
{
    "outcome" => "success",
    "result" => {
        "operation-name" => "stop",
        "description" => "Tell reverse proxies that all contexts on the node can't process requests.",
        "request-properties" => {"waittime" => {
            "type" => INT,
            "description" => "Timeout to wait for all contexts to stop.",
            "expressions-allowed" => false,
            "required" => false,
            "nillable" => true,
            "default" => 10,
            "unit" => "SECONDS"
        }},
        "reply-properties" => {},
        "read-only" => false,
        "runtime-only" => true
    }
}

      With default and non-distributable context or draining strategy set to ALWAYS.

      • stop() or stop-context is called
      • Disable creating any new session by sending DISABLE-APP command to balancer
      "context" => {"/clusterbench" => {
                        "requests" => 0,
                        "status" => "disabled"
                    }}
      • Session drain
      2017-05-10 09:19:09,956 INFO  [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds.
      • Session timeout is 5 minutes so it fails
      2017-05-10 09:26:05,081 WARN  [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds

      Issue

      • Stop-app should be sent to balancer to stop context/node, but node/context stays disabled. This happens even if session drain is successful. 
        "context" => {"/clusterbench" => {
                        "requests" => 0,
                        "status" => "disabled"
                    }}

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-596 mod_cluster stop/stop-context operations do not send STOP-* in when session draining was unsuccessful

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-10839 Upgrade mod_cluster to 1.3.7.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11872 mod_cluster stop/stop-context operation results do not inform whether session draining was successful

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12256 mod_cluster stop status is not updated in balancer/node resource

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10356 mod_cluster stop/stop-context(waittime=..) attribute description is wrong

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              bsikora Bogdan Sikora (Inactive)
              Bogdan Sikora Bogdan Sikora (Inactive)
              Bogdan Sikora Bogdan Sikora (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: