I'm just getting ready to ask a question like this, as I have a similar need.
I'm using the built-in Tribes-based replication which works fine for short periods of time and under moderate to light load. Once the Tomcat server has been running for a day or two, though, this distributed session replication starts breaking unexpectedly. Once this happens, the apps start becoming unavailable until I restart everything. I'm trying to figure out today how I can implement a Valve or something that can store a session to a backend DB and reload that session on another Tomcat instance similar to how the PersistentManager loads user's session after a restart. Would a Valve based on PersistentValve allow me to implement a cluster-like solution such that a user login causes a write to a central database and a load balanced request to another server would see that user without forcing another login? Jon Brisbin Portal Webmaster NPC International, Inc. On Feb 15, 2010, at 11:05 AM, Simone Tripodi wrote: > Hi all guys and very nice to meet the Tomcat community, > I've a web-application that needs to be replicated in more than one > Tomcat, and since it is HttpSession based, I need to enable the > session replication. > Even if I work with very good sysadmins that know how to do it, I'm > curious and would like to know if I could replace the HttpSession > implementation with a my own one, I'd like to integrate Hazelcast[1] > for data synchronization. > Thanks in advance, every suggestion will be very appreciated. > Simo > > [1] http://www.hazelcast.com/ > > http://people.apache.org/~simonetripodi/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
