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

mod_cluster session draining with non-positive timeout may wait indefinitely

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.ER2
    • 7.1.0.DR16, 7.1.0.DR17
    • 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 with waittime set to 0
      Session drain

      2017-05-10 09:18:21,953 INFO  [org.jboss.modcluster] (management-handler-thread - 2) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 0 seconds.

      Issue
      This should immediately fail to drain session and send stop node/context to balancer.
      However, it looks like it is waiting for session to timeout

      Context/Node is disabled on balancer

      "context" => {"/clusterbench" => {
                        "requests" => 0,
                        "status" => "disabled"
                    }}

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-581 Session draining with non-positive timeout may wait indefinitely

          • 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-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:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: