Uploaded image for project: 'Spring Framework'
  1. Spring Framework
  2. SPR-13451

DeferredResult not thread-safe for isSetOrExpired call

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Complete
    • Affects Version/s: 3.2.14, 4.1.7, 4.2.1
    • Fix Version/s: 3.2.15, 4.1.8, 4.2.2
    • Component/s: Web
    • Labels:
      None
    • Last commented by a User:
      true

      Description

      The use of DeferredResult is usually from other threads than the one it was created on.

      Clients may call isSetOrExpired to check the state of the result: however this may return stale information as it has no synchronization, unlike the setResultInternal method, which synchronizes.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              juergen.hoeller Juergen Hoeller
              Reporter:
              JHodkinson Jamie Hodkinson
              Last updater:
              Spring Issues Spring Issues
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                3 years, 30 weeks, 3 days ago