Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-7497

Incorrect value returned by undertow for "max number of concurrent active sessions" metric

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Alpha1
    • None
    • Web (Undertow)
    • None
    • Hide

      1. Deploy [^helloworld.war] file.
      2. Connect to server using CLI (jboss-cli.sh)
      3. Request the metric: /deployment=helloworld.war/subsystem=undertow:read-attribute(name=max-active-sessions)

      The server is returning:

      [standalone@localhost:9990 /] /deployment=helloworld.war/subsystem=undertow:read-attribute(name=max-active-sessions)
{
    "outcome" => "success",
    "result" => -1
}

      The server is returning -1 because this is the default value for unlimited sessions. If you deploy [^helloworld2.war] file, the server returns 2 for that deployment, this is the maximum allowed session configured in the war file. (jboss-web.xml max-active-sessions).

      [standalone@localhost:9990 /] /deployment=helloworld2.war/subsystem=undertow:read-attribute(name=max-active-sessions)
{
    "outcome" => "success",
    "result" => 2
}

      This is not the maximum number of concurrent sessions metric that we expected.

      Show
      1. Deploy [^helloworld.war] file. 2. Connect to server using CLI (jboss-cli.sh) 3. Request the metric: /deployment=helloworld.war/subsystem=undertow:read-attribute(name=max-active-sessions) The server is returning: [standalone@localhost:9990 /] /deployment=helloworld.war/subsystem=undertow:read-attribute(name=max-active-sessions) { "outcome" => "success" , "result" => -1 } The server is returning -1 because this is the default value for unlimited sessions. If you deploy [^helloworld2.war] file, the server returns 2 for that deployment, this is the maximum allowed session configured in the war file. (jboss-web.xml max-active-sessions). [standalone@localhost:9990 /] /deployment=helloworld2.war/subsystem=undertow:read-attribute(name=max-active-sessions) { "outcome" => "success" , "result" => 2 } This is not the maximum number of concurrent sessions metric that we expected.

    Description

      Undertow is returning "maximum active sessions allowed" configured in the deployment as the "max number of concurrent active sessions" metric.

      Additional Information:

      I requested a resource description and the description of the attribute says it is a metric.

      [standalone@localhost:9990 /] /deployment=helloworld2.war/subsystem=undertow:read-resource-description 
.......
.......

            "max-active-sessions" => {
                "type" => INT,
                "description" => "*Max number of concurrent active sessions*",
                "expressions-allowed" => false,
                "nillable" => false,
                "access-type" => "metric",
                "storage" => "runtime"
            },
.....
.....

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4440 Incorrect value returned by undertow for "max number of concurrent active sessions" metric

          • 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

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              sdouglas1@redhat.com Stuart Douglas
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: