Re: Issue 80 in glassdb: RcKeyValueDictionary conflicts (Seaside3.0 and Swazoo)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Issue 80 in glassdb: RcKeyValueDictionary conflicts (Seaside3.0 and Swazoo)

glassdb
Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.8.7

Comment #4 on issue 80 by [hidden email]: RcKeyValueDictionary  
conflicts (Seaside3.0 and Swazoo)
http://code.google.com/p/glassdb/issues/detail?id=80

I (presumably) saw this particular issue when load testing SS3 and started  
using WARcLastAccessExpiryPolicy for managing the session cache as well ...  
Previously WARcLastAccessExpiryPolicy was only used for managing the  
configuration cache,,,

Name: Seaside-Session.gemstone-dkh.140
Author: dkh
Time: 05/31/2011, 15:23:39
UUID: 39b070e0-244c-4c35-887e-a7ff1287c491
Ancestors: Seaside-Session.gemstone-dkh.139

- use WARcLastAccessExpiryPolicy to avoid unnecessary commit conflicts  
under load