Oops forgot to remove test code.
git-svn-id: svn+ssh://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk@1219 7e9141cc-0065-0410-87d8-b60c137991c4
Remove LightLoad test as this is not applicable for the JDBC solution. It only works with terracotta because terracotta takes out a cluster-wide lock when the session is entered on any node. This means you can bounce the session around nodes. This does not work with the JDBC session implementation as it is not feasible to do a cluster-wide lock on particular row on the sessions table.
Add a method on JDBCSessionManager that would allow a subclass to send a message to all other nodes whenever the session is being written to the database which would cause the other nodes to invalidate that session in their local caches and re-read from the database.
git-svn-id: svn+ssh://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk@1218 7e9141cc-0065-0410-87d8-b60c137991c4
Changes to JDBCSessionIdManager with this checkin were to increase the length of the varchar storing the session id from 60 to 120 char, and also to reduce the amount of time we held a lock over the session id map.
Changes to the JDBCSessionManager with this checkin were to decrease the amount of time we held locks, and when retrieving a session from the database, checking if the session had expired before loading it.
Changes to the AbstractSessionManager with this checkin were to ensure that the SessionListeners were only called if the session was removed (we were calling them anyway).
git-svn-id: svn+ssh://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk@1213 7e9141cc-0065-0410-87d8-b60c137991c4
Jan Bartel