hazelcast/hazelcast — pull request #109 by Nugs (2012-04-04 12:24:32+00:00)
Title: Programmatic session destruction wasn't leading to the destruction of the clustered session (Issue #104)

The clustered session SHOULD always be destroyed when a programmatic invocation of invalidate() is made IRRESPECTIVE of whether the session's timeout threshold has been reached or not.

This change introduces an 'ignoreTimeout' parameter to the destroySession method which is 'true' for programmatic invocations but 'false' when invoked via the SessionListener - meaning that the clusterwide session will be checked for lastAccessedTime before it's considered for invalidation.

Relates to (and fixes) issue #104 as invalid sessions are no longer maintained in the cluster (and cannot therefore be looked up) in the post chain portion of the WebFilter.