This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
The company I am working for is trying to get our application to Enterprise strength and have been working on server failover issues. I've never had to solve a solution like this before and was hoping for some advice.
As of right now I'm not a fan of the current clustering solution that is offered by tomcat and have decided to try and use the PersistentManager/JDBCStore solution.
Unfortuanantly using the PersistentManager the HttpSession gets written to the database about 10 to 15 seconds after a new HttpSession gets created.
We wrote a custom HttpSessionAttributeListener that listens for the one attribute we actually store in our HttpSession and when we receive that event we persist the session to the Database.
Will this solution work for server failover for an Enterprise system?
I like this solution because in theory we don't have to ever worry about adding clustering to the server.xml and in theory we don't ever have to worry about bringing down a server or set of servers if we need to.