Support session-timeout of 0 or less (no session expiration)

[GoogleCodeExporter]

The servlet spec (2.5/3.0: SRV.13.4 Deployment descriptor) says that if the 
session-timout is 0 or less that by default sessions never expire (while 
setMaxInactiveInterval(0) causes a session.expire()).

Right now this is not supported by msm as the session timeout is used to 
determine the expiration in memcached. A session stored in memcached with a 0 
or negative expiration will not be returned by memcached on subsequent requests.

If the application uses a session-timeout <= 0 the session should be stored 
with the maximum possible expiration in memcached.

Original issue reported on code.google.com by martin.grotzke on 12 Mar 2011 at 8:15

[GoogleCodeExporter]

Original comment by martin.grotzke on 12 Mar 2011 at 8:15

• Changed title: Support session-timeout of 0 or less (no session expiration)

[GoogleCodeExporter]

Fixed in master and tomcat7 branch.

Original comment by martin.grotzke on 12 Mar 2011 at 10:19

• Changed state: Fixed