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

(7.0.x) wrong conversion for response time when requested in seconds

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.3.CR1, 7.0.3.GA
    • 7.0.1.GA
    • Undertow
    • None
    • Hide

      Tested with EAP 7.0.1:
      1. Start EAP and connect to CLI
      2. /subsystem=undertow/server=default-server/host=default-host/setting=access-log:add(extended=true,pattern="time-taken")
      3. /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=record-request-start-time,value=true)
      4. reload
      5. deploy attached testing war app [^long-running-servlet.war]
      6. perform request on server, e.g.: http://localhost:8080/long-running-servlet/HeavyProcessing?duration=6000 and see content in EAP_HOME/standalone/log/access_log.log file

      Show
      Tested with EAP 7.0.1: 1. Start EAP and connect to CLI 2. /subsystem=undertow/server=default-server/host=default-host/setting=access-log:add(extended=true,pattern="time-taken") 3. /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=record-request-start-time,value=true) 4. reload 5. deploy attached testing war app [^long-running-servlet.war] 6. perform request on server, e.g.: http://localhost:8080/long-running-servlet/HeavyProcessing?duration=6000 and see content in EAP_HOME/standalone/log/access_log.log file
    • EAP 7.0.3

      There is a bug in Undertow's way of converting response time to seconds format for access log. In milis variable is expected to be time in milliseconds but as timeUnit is TimeUnit.SECONS actually, there are just seconds after such conversion.

      You can see it for example when use 'time-taken' identifier in access log and perform some long running request - see 'Steps to Reproduce' section.

              jstourac@redhat.com Jan Stourac
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: