The Javadoc states "Set sticky_session to False when Tomcat is using a Session Manager which can persist session data across multiple instances of Tomcat." Would use of PersistentManager with JDBCStore qualify as persisting session data across multiple instances of Tomcat? Or, does this refer only to in memory replication? I tried using non-sticky sessions with the PersistentManager but the sessions would become stale due to the delay between the time the session is modified and the time the JDBCStore actually gets updated. I guess I've pretty much answered my own question ( does NOT apply ) but I wanted to verify it. Is there any why to configure the PersistentManager so that a call to setAttribute would synchronously update the JDBCStore? Thanks, Gary
