fellow JRunners, Just out of curiosity, is anyone actually running their production servers with session persistence between server restarts enabled?
We develop and sell a complex servlet(not any EJBs yet...) based strategy/people/project/task managment application, with extensive memory caching of database data. Our Consulting guys are begging us to support the session persistence between server restarts functionality, to allow them to bring down customer servers, patch them, and start them again, without each and every user noticing (except for a delay). But us developers hesitate... We see several potential problems, with data inconsistency between data in a users session (stored between restarts), data in cache (flushed) and data in the database (flushed) beeing the largest. There could also be potential problems with new versions of class files for objects that are persisted. Are we beeing paranoid? Is it reasonable to expect a complex web app to support session persistence between server restarts perfectly, or is it acceptable to not support it? ~ Tormod ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Tormod Hystad Senior Developer, R&D CatalystOne, Inc. - Execution excellence! ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
