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

If trace logging is enabled in EntryWrappingInterceptor, a moderate number of keys could kill state transfer.

    Details

      Description

      In EntryWrappingInterceptor.visitInvalidateL1Command there is a trace log that prints the entire context, including any wrapped keys. If you're debugging state transfer, a moderate number of keys can crush state transfer. For the size of the key array, it'll print 1, then 1+2, then 1+2+3, ... 1+2+3+...n.

      This is low priority to be sure, but maybe the trace check should be outside the for loop?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                william.burns Will Burns
                Reporter:
                an1310 Erik Salter
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: