-
1. Re: Impact of enabling "invocationBatching" without using it
mircea.markus Nov 29, 2013 12:33 PM (in response to fertroya)1 of 1 people found this helpfulI guess you have the autocommit attribute[1] set to true (which is the default). What happens is that infinispan starts and completes a transaction for each operation you perform. Disable autocmmit and you should get an exception.
[1] http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_backward_compatibility
-
2. Re: Re: Impact of enabling "invocationBatching" without using it
fertroya Nov 29, 2013 12:52 PM (in response to mircea.markus)Oh sorry, I think I didn't make myself clear.
This is an excerpt of the configuration:
<default> ... <invocationBatching enabled="true" /> <transaction transactionMode="TRANSACTIONAL" ..> </transaction> ... </default>
I forgot to mention we're using INFINISPAN 5.1.5 which, as you mention, has autoCommit enabled by default.
What I want to know is if declaring invocationBatching here makes any sense; given that in java code no batchs are created and that transactionMode is already declared as TRANSACTIONAL.
Cheers
-
3. Re: Re: Impact of enabling "invocationBatching" without using it
mircea.markus Dec 2, 2013 9:11 PM (in response to fertroya)What I want to know is if declaring invocationBatching here makes any sense; given that in java code no batchs are created and that transactionMode is already declared as TRANSACTIONAL.
No, it doesn't help. If anything it slows down things - shouldn't be noticeable though.
I strongly recommend moving to a newer inifinispan version: there's been a lot of performance and functionality improvements since 5.1.x