-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Ehcache and "manual" 2-node cluster invalidation
PostPosted: Wed Feb 23, 2005 6:47 am 
Newbie

Joined: Mon Sep 27, 2004 2:15 am
Posts: 11
Location: Helsinki, Finland
We've got 2 servers in our cluster and we're using Hibernate 2.1.7c. We have three legacy databases sharing the same schema but with different data, so we have three SessionFactories. Currently, we have permission to use Ehcache, and JBossCache permission is pending but who knows when we'll be able to take it into use.

Thus we need a solution for using Ehcache in our cluster. This is what we came up with -- what do people think?

Deploy and configure ehcache on each server. Create an Interceptor that catches flushes, saves, and deletes and delivers an eviction notice JMS message to the other server node with the session factory identification, the object class, and object id. The other node then grabs the right session factory and evicts the object.

Sure, this comes under the category of "hack", especially when there are products like JBossCache and Tangosol Coherence available, but like I said, for the time being, we're stuck with ehcache.

Thoughts, comments?


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.