Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-752

Duplicate response after async response timeout

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 2.3.5.Final
    • 2.3.4.Final
    • None
    • None
    • Hide

      1. Run the war file, ROOT.war
      2. Connect to http://localhost:8080/timeoutStacks
      3. Wait for timeout, make sure server returned 200 (another bug, should be 408)
      4. Again, connect to http://localhost:8080/timeoutStacks and see that two responses are returned, the previously timeout response and then the current one.

      NOTE: tomcat has a 10sec default timeout, and Jetty has a 30sec timeout.

      Show
      1. Run the war file, ROOT.war 2. Connect to http://localhost:8080/timeoutStacks 3. Wait for timeout, make sure server returned 200 (another bug, should be 408) 4. Again, connect to http://localhost:8080/timeoutStacks and see that two responses are returned, the previously timeout response and then the current one. NOTE: tomcat has a 10sec default timeout, and Jetty has a 30sec timeout.

      The problem I'm experiencing is that a REST call, handled by RESTEasy, appends the result of all the previously timed out requests, which failed due to the asyncContext.complete() exception. If I submit "X" separate calls that block longer then then timeout and then submit a call which processes quickly the result will contain X+1 copies of the data. I'm able to reproduce this very easily. I can attach a war file as an example if possible.

        1. ROOT.war
          5.67 MB
        2. AsyncController.java
          2 kB
        3. async-http-servlet-3.0-2.3.5.Final.jar
          7 kB
        4. async-http-servlet-3.0-2.3.5.Final-sources.jar
          4 kB
        5. async-http-servlet-3.0-2.3.5.Final.jar
          8 kB
        6. async-http-servlet-3.0-2.3.5.Final-sources.jar
          4 kB

              rsigal@redhat.com Ronald Sigal
              mvanwely_jira Matt Van Wely (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 1 week
                  1w
                  Remaining:
                  Remaining Estimate - 1 week
                  1w
                  Logged:
                  Time Spent - Not Specified
                  Not Specified