[infinispan-dev] Fwd: Transaction Semantics when using CacheLoaders and CacheWriters

2013-08-05 Thread Galder Zamarreño
A very interesting thread in the JSR-107 group, which appears just as Mircea has looked into the XA transactions and cache loaders/stores. Going back to that thread, it wasn't very clear what would happen if Infinispan caches were configured with XA transactions and they had a cache store.

[infinispan-dev] Query regarding Infinispan Clustering Performanc​e

2013-08-05 Thread Faseela K
Hi, I am doing some analysis and study to see how the performance of infinispan can be improved in distributed clustered mode. This study is based on some performance test I ran, with 3 nodes, where replication performance seems better than distribution. But, I think distribution

[infinispan-dev] Infinispan 6.0.0.Alpha2 is out!

2013-08-05 Thread Dan Berindei
Dear Infinispan community, We're proud to announce the second Alpha release of Infinispan 6.0.0, and also the second release using the Apache Software Licence. New features in this release: - A new query DSL https://issues.jboss.org/browse/ISPN-3169 that is usable both in embedded/library

[infinispan-dev] Config of RemoteCacheStore(s) in HR RollingUpgrades

2013-08-05 Thread Tomas Sykora
Hello guys, Tristan is on PTO and it would be very helpful for me if someone can comment here please: https://community.jboss.org/wiki/RollingUpgradesForRemoteClientsUsingHotRod#comment-12493 @Manik? Thank you in advance! Tomas ___ infinispan-dev

Re: [infinispan-dev] storeAsBinary keeps both the object and the byte[] - why?

2013-08-05 Thread Galder Zamarreño
Hi, Sorry for the delay getting back on this topic. Let me start with a little side node: I've been trying to find a previous discussion where I wondered about the merits/complexity/need of storeAsBinary. I'm pretty sure I made a point in the past about whether it was really useful but can't

Re: [infinispan-dev] storeAsBinary keeps both the object and the byte[] - why?

2013-08-05 Thread Manik Surtani
On 18 Jul 2013, at 13:44, Mircea Markus mmar...@redhat.com wrote: Can anybody think of some reasons why the value is kept twice? I mean besides optimising for local gets, which I think is not a good enough reason given the potentially huge memory consumption and the complexity added. It is

[infinispan-dev] storeAsBinary + lookup

2013-08-05 Thread Ales Justin
Anything obvious on why this lookup doesn't find its match? Some background: * I have .ear, with 2 .war sub-deployments * each .war has own Key class in own gae.jar (in WEB-INF/lib) I do set storeAsBinary on the cache, which is shared between both .wars. This first key is the key for 2nd

Re: [infinispan-dev] storeAsBinary + lookup

2013-08-05 Thread Ales Justin
Forgot to mention: Put was done in 1st .war, where get is done in 2nd .war. @Test @InSequence(1) @OperateOnModule(m1) public void testPut() throws Exception { Key key = ds.put(new Entity(MODULES_KIND, 1)); Assert.assertNotNull(key); } @Test