• Bug
  • Status: Open
  • 3 Minor
  • Resolution:
  • ehcache-jmsreplication
  • Reporter: sourceforgetracker
  • September 21, 2009
  • 0
  • Watchers: 0
  • January 06, 2010


JBossMQ does not provide a properietary reconnect feature. If JMS is not available JMS replication will be gone forever. To investigate that, I moved most JMS code to JMSCachePeer.java. This is probalby not necessary: I merely missed it on my first reconnect tests to call ‘dispose’ on JMSCachePeer, since without it the topic session will get stale and therfore unusable. Anyway, it works now quite reliable, except in some obscure situations when there is no JMS ReplicationThread created by ehcache, which is also fatal, but another story ;) Sourceforge Ticket ID: 2808944 - Opened By: mbclr - 19 Jun 2009 10:32 UTC


Fiona OShea 2010-01-06

Assigning these issues to Greg, so that he can decide what to do with them.