[infinispan-dev] Flags ignored during batch operations

[Sanne Grinovero]

Hello,
I was quite surprised to hit a timeout on lock acquire on a method
flagged with SKIP_LOCKING.

Debugging I've found that in case a batch operation is running and no
transaction is active org.infinispan.interceptors.BatchingInterceptor
creates a new InvocationContext, ignoring the existing one, and so the
invocation proceeds but the flags I defined are cleared.

What is the reason to create a new InvocationContext? Could that be
changed to at least carry over the defined flags?

I've been playing with it by using setFlags(existingFlags) and have
already experienced another little performance boost with Lucene,
especially as it's now respecting SKIP_REMOTE_LOOKUP too, but I'm not
going to change this without understanding.

Sanne