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

Cacheable key collision with DefaultKeyGenerator

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.2 GA
    • 4.0 M2
    • Core
    • 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

              pwebb Phil Webb
              ethlo Morten Haraldsen
              Spring Issues Spring Issues
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                3 years, 38 weeks, 1 day ago