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

[Dan Berindei (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Berindei resolved ISPN-4143.
--------------------------------
         Assignee: William Burns
    Fix Version/s: 6.0.0.Final
       Resolution: Done


Fixed with ISPN-3633.

> 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: William Burns
>             Fix For: 6.0.0.Final
>
>
> 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 was sent by Atlassian JIRA
(v6.3.11#6341)