Hi Ashish, I created a memcached based session failover solution: http://code.google.com/p/memcached-session-manager/
Basically it stores session information in memcached so that they can be pulled from memcached if they are not available in the local session map. For a normal request, the session is read from the local session map (in-memory). One advantage over the PersistentManager is, that I also created an xml based serialization strategy that supports different versions of a class (e.g. the msm-javolution-serializer, see [1] for more) - this is especially useful if you deploy a new version of your software and your serialized classes changed. With the standard java serialization deserializing session will fail, the xml based approach is able to handle this. Other advantages over the database storage target scalability, that was the main motivation why I created this project. Cheers, Martin On Wed, 2010-02-03 at 00:28 -0500, Ashish Kulkarni wrote: > Hi > Is it possible with tomcat to save session information in database or some > where which can be retrieved after restart, for example raisin > provides symmetrical > session which can be saved to database or file system > [1] http://code.google.com/p/memcached-session-manager/wiki/SerializationStrategies -- Martin Grotzke http://www.javakaffee.de/blog/
signature.asc
Description: This is a digitally signed message part
