Heads Up - EHCache replication under JTA, a total failour
lately i've been trying to use EHCache 2.x latest feature - replication under JTA.
the documenation is pretty coherent and easy, and I had a POC in no time.
here where the easy part ends...
it seems that EHCache replication without JTA works fine, EHCahce JTA without replication works fine also.
the problem is that replication with JTA is not working, at all, under any 2.x version I've tried.
I've even tried every protocole that is specified in the documentation - RMI, JGroups and JMS, nothing works.
Here's Taylor Gautier's (Product Manager, Terracotta) response as to JTA support (origianl post) -
"The Java memory model is not hooked in with JTA, and so Terracotta does not support JTA. If you are using JTA to write across more than one system, and that is a hard requirement, then you might need to look elsewhere for a while. However, we find that most people really don’t need full 2pc – it’s too slow and not really needed. What you do need is stable, restartable, durable memory, and Terracotta does give you that."
after experiencing with the latest replication-JTA support I came to the conclusion that the Terracotta team still think it's not important.
there's no other explanation for the poor support of this feature in 2.x verions.
dont get me wrong, I love EHCache and I think it's a great open source.
but since it doesn't support what it claims to (which pretty much sucks for their reputation) it's useless for my current POC.
hopefully the EHCache team will fix this feature (and mindset). in my opinion a replication under JTA is a greate feature for J2EE application.
my next step is to check JBossCache, which claims to support this feature. POC report will follow soon...