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

Cacheable key collision with DefaultKeyGenerator

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.2 GA
    • Fix Version/s: 4.0 M2
    • Component/s: Core
    • Labels:
      None

      Description

      The default is to use the hashcode of each parameter and create another (32-bit) hash code. Obviously this can easily generate collisions. This should be clearly documented as it feels like a pretty serious issue, if not a bug. We have come to expect that Spring defaults are "safe"

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                pwebb Phil Webb
                Reporter:
                ethlo Morten Haraldsen
                Last updater:
                Rob Winch
              • Votes:
                3 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  5 years, 26 weeks ago