Hi Donald, unfortunatly SQS would not allow to have a transactional cache as there is a possible delay of 20sec until a message can be fetched and it is designed that only one instance consumes the message.
ehcache: Wouldn't the ehcache-jgroups replication (http://ehcache.org/documentation/distributed_caching_with_jgroups.html ) do the job as it would propagate put,update,delete to all members. I assume one need only to configure the cache for svjm and let ehcache+jgroup do the eviction. There is already a ehache-openjpa plugin (http://ehcache.org/documentation/openjpa_provider.html) What do you think? Thanks, Oliver -- View this message in context: http://openjpa.208410.n2.nabble.com/configure-RemoteCommitProvider-for-Amazon-EC2-tp5064783p5068597.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
