Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-8798

ByteString places too strict a constraint on cache name length

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 9.1.5.Final, 9.2.0.CR2
    • Fix Version/s: 9.1.6.Final, 9.2.0.CR3
    • Component/s: Core
    • Labels:
      None

      Description

      The hibernate 2nd level cache code can easily generate cache names that exceed the byte length restriction enforced by ByteString. Cache names are generated using the fully qualified class name of the entity, which are user defined, and in the case of WildFly, also includes the deployment name, which can be particularly long for EARs.
      At the very least, we should use an unsigned byte which doubles the allowed size. Why not also consider using https://github.com/infinispan/infinispan/blob/master/commons/src/main/java/org/infinispan/commons/io/UnsignedNumeric.java to marshal/unmarshal the size of the byte[] containing the name? At worst, this costs an extra byte, but solves the size problem for even sizes larger than 255.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pferraro Paul Ferraro
                  Reporter:
                  pferraro Paul Ferraro
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: