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

session-max-alive-time statistics for deployment are counted incorrectly

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Alpha1
    • 10.1.0.Final
    • Web (Undertow)
    • None
    • Hide
      1. Start EAP 7
      2. Enable statistics collecting for undertow (via CLI /subsystem=undertow:write-attribute(name=statistics-enabled, value=true))
      3. Deploy application with servlet which uses sessions (ideally setup session timeout to 1 minute), attached simple-servlet.war which contains such servlet
      4. Create request to that servlet curl -i http://127.0.0.1:8080/simple-servlet/counter -c cookie.txt -b cookie.txt
      5. wait for the session to expire (wait more than 1 minute, you can then try another request to see it has expired)
      6. check the statistics => run via CLI /deployment=simple-servlet.war/subsystem=undertow:read-resource(include-runtime=true) and see that session-max-alive-time is updated but instead value close to 60 => 60s as session expiration is set to 1 minute it shows much higher number
      Show
      Start EAP 7 Enable statistics collecting for undertow (via CLI /subsystem=undertow:write-attribute(name=statistics-enabled, value=true) ) Deploy application with servlet which uses sessions (ideally setup session timeout to 1 minute), attached simple-servlet.war which contains such servlet Create request to that servlet curl -i http://127.0.0.1:8080/simple-servlet/counter -c cookie.txt -b cookie.txt wait for the session to expire (wait more than 1 minute, you can then try another request to see it has expired) check the statistics => run via CLI /deployment=simple-servlet.war/subsystem=undertow:read-resource(include-runtime=true) and see that session-max-alive-time is updated but instead value close to 60 => 60s as session expiration is set to 1 minute it shows much higher number

    Description

      The value of session-max-alive-time is incorrectly counted. It looks as it is counted in miliseconds instead of seconds + the value is double of expected one.

      Attachments

        Issue Links

          Activity

            People

              chaowan@redhat.com Chao Wang
              chaowan@redhat.com Chao Wang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: