Issue 342 in glassdb: session and continuation default expiry not synchronized

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Seaside Version-3.0.x

New issue 342 by [hidden email]: session and continuation default  
expiry not synchronized
http://code.google.com/p/glassdb/issues/detail?id=342

See the discussion[1] for details and information about whether the  
proposed workaround works.

Using:

   (WAAdmin defaultDispatcher handlers at: 'myAplicationName') cache
     expiryPolicy configuration at: #cacheTimeout put: 1200

will change the session expiry to 20 minutes, but the session continuation  
cache expiry is untouched and left at the default 5 minutes which can cause  
problems under certain conditions. it appears that the only way to affect  
the continuation expiry is to wire in a timeout as follows (in  
WASession>>createCache):

     createCache
         "To configure the continuation cache you must currently subclass  
WASession and
         override this method."

         | policy |
         policy := WARcLastAccessExpiryPolicy new.
         policy configuration at: #cacheTimeout put: 1200.
         ^ WACache new
                 setExpiryPolicy: policy;
                 yourself.

which is not ideal ... at this time it is not certain that this is actually  
addressing the issue, but I have inspected the various instances involved  
in my setup and can see that the timeouts are not synchronized and if a  
page is left unattended for 5 minutes all of the continuations on that page  
will have timed out and that is probably the condition that they are  
seeing ...

I did validate that the sessions themselves will survive themselves for the  
correct timeout...



[1] http://forum.world.st/Set-session-duration-td4553027.html