On 30 Jul 2013, at 23:12, Sanne Grinovero sa...@infinispan.org wrote:
My experience with transactions is limited, so I likely am missing on
some base concept, but I don't understand why the fact that it's
running on a different process is limiting in any form. We do that
regularly from
On 31 July 2013 16:01, Mircea Markus mmar...@redhat.com wrote:
On 30 Jul 2013, at 23:12, Sanne Grinovero sa...@infinispan.org wrote:
My experience with transactions is limited, so I likely am missing on
some base concept, but I don't understand why the fact that it's
running on a different
Sent from my iPhone
On 31 Jul 2013, at 17:01, Sanne Grinovero sa...@infinispan.org wrote:
On 31 July 2013 16:01, Mircea Markus mmar...@redhat.com wrote:
On 30 Jul 2013, at 23:12, Sanne Grinovero sa...@infinispan.org wrote:
My experience with transactions is limited, so I likely am
Hi,
I don't think can support XA (JTA) enabled cache stores. Here's why:
- C1 (cache store instance) runs on node N1
- an JTA tx is started on N2 which writes to(has a key that maps to) N1 - both
to the DataContainer and C1.
- the JTA transaction manager running the transaction resides on N2, so
My experience with transactions is limited, so I likely am missing on
some base concept, but I don't understand why the fact that it's
running on a different process is limiting in any form. We do that
regularly from appservers, queues, RDBMS's, ... ?
In this case the Infinispan node N1 needs to
://infinispan-developer-list.980875.n3.nabble.com/infinispan-dev-CacheStore-redesign-no-XA-cache-stores-tp4027770p4027772.html
Sent from the Infinispan Developer List mailing list archive at Nabble.com.___
infinispan-dev mailing list
infinispan-dev
