Description
In EntryWrappingInterceptor.visitInvalidateL1Command there is a trace log which does not check if the trace is enabled - with invalidate command with a lot of keys (such as in case of ST) this would construct for each of these keys really long strings (with all the keys...), and then throw it off.
Moreover, the InvalidateL1Command is still built even if I don't have L1 enabled, but that's another issue.