• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • ehcache-core
  • alexsnaps
  • Reporter: alexsnaps
  • March 15, 2010
  • 0
  • Watchers: 1
  • May 21, 2010
  • March 18, 2010


The copy-on-read flag is set too late on the Terracotta config, resulting in the store being misconfigured. This can be worked around by setting copyOnRead=”true” to the of the XA cache manually


Tim Eck 2010-03-15

This should be the topic of another JIRA, but we could consider making copyOnRead a dynamic (and maybe even local/transient) property). This might be what people want and it would have avoided this bug too :-)

Alexander Snaps 2010-03-15

Thought this would justify another question I asked myself earlier today. Where do I best force the store to be copyOnRead if the cache is configured to be transactional… I was thinking whether that should not be state/decisions taken in the config itself. Haven’t looked any further if something comparable had been done before, but I’ll be asking myself the question again soon I think!

Tim Eck 2010-03-15

I dunno really the best place. The way the code is right now seems pretty straightfoward the setting of copyOnRead to true is located along with the creation of the XA store. Of course that doesn’t work, but the placement seems reasonable

Alexander Snaps 2010-03-18

Tests are in terracotta-ehcache as of: r21197 on tc-3.2 branch r21198 on trunk

Himadri Singh 2010-05-10

tests are running on monkeys