[infinispan-issues] [JBoss JIRA] (ISPN-4143) If trace logging is enabled in EntryWrappingInterceptor, a moderate number of keys could kill state transfer.

[Erik Salter (JIRA)]

Erik Salter created ISPN-4143:
---------------------------------

             Summary: If trace logging is enabled in EntryWrappingInterceptor, a moderate number of keys could kill state transfer.
                 Key: ISPN-4143
                 URL: https://issues.jboss.org/browse/ISPN-4143
             Project: Infinispan
          Issue Type: Bug
          Components: State Transfer
    Affects Versions: 5.2.7.Final
            Reporter: Erik Salter
            Assignee: Dan Berindei


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?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira