Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-7140

Multiple calls to AsyncResponse.cancel() returns different values

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.1.8
    • 3.1.9, 3.0.12, 3.2.0
    • JAX-RS
    • None
    • Moderate

    Description

      When we incorporated CXF 3.1.8 into our builds, our CTS testing team found some failures related to the AsyncResponse.cancel(...) methods. According to the spec, once the AsyncResponse has been canceled, subsequent calls to cancel should return true.

      It looks like one of the changes in CXF-7037 changed the order of things in the doCancel method – and those changes result in false getting returned when calling cancel(...) a second time.

      I have written some tests that demonstrate the expected CTS behavior - and they fail with the current code, but pass when reverting the order change in doCancel().

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            sergey_beryozkin Sergey Beryozkin
            andymc Andrew J McMurry
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment