On Sep 13, 2011, at 6:38 PM, Mircea Markus wrote:
On 13 Sep 2011, at 17:22, Galder Zamarreño wrote:
> Hi,
>
> I'm looking at this failure
http://goo.gl/NQw4h and I'm wondering why
"org.infinispan.distribution.RehashInProgressException: Timed out waiting for the
transaction lock" is thrown?
>
> This is thrown DistTxInterceptor which is added by the InterceptorChainFactory:
>
> if (configuration.getCacheMode().isDistributed())
>
interceptorChain.appendInterceptor(createInterceptor(DistTxInterceptor.class));
> else
> interceptorChain.appendInterceptor(createInterceptor(TxInterceptor.class));
>
> However, this is a Hot Rod test and the cache is not configured with a transaction
manager, so is DistTxInterceptor really needed?
>
> In fact, why a TxInterceptor if no transaction manager is configured? (this kinda
goes back to Mircea's email earlier today about a transactions enabled/disabled flag)
All valid concerns, IMO.
5.1 will clarify this by not adding Tx interceptors for non tx caches.
Is this captured in some other JIRA? I'd like to reference the test and the JIRA from
ISPN-1123 (stabilising testsuite jira)
>
> Cheers,
> --
> Galder Zamarreño
> Sr. Software Engineer
> Infinispan, JBoss Cache
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache