> Did you configure the faster SDC to disable the 'lazy' flag?  That flag
> disables modification of the SDC's linked list until the sesion is
> actually modified, rather than being just accessed as you are doing here.
I tried both, with and without 'lazy' setting.
I used _BUCKET_TYPE = AppendOnlyDict, timeout set to 1200 and timeout
resolution: 20

I did three concurrent requests (from three browsers) twice (first
request was just to initially create session data objects).
With second request, lazy or not, every time I get errors like these
attached below. Function that is called sleeps for 50 seconds and just
gets the access to SESSION object - doesn't put anything into session.
I've added print statements to _p_resolveConflict too
but seems this function is only called once in this situation.
In general tuning up session resolution seconds helps here.

Thanks for your answers I've read about Faster storage and I think
I understand this much more now, although I'm not sure about conflicts
below.

(...)
2007-04-12 21:43:28 DEBUG txn.1090525536 new transaction
testme started
2007-04-12 21:43:29 DEBUG txn.1098918240 new transaction
testme started
2007-04-12 21:43:30 DEBUG txn.1082132832 new transaction
testme started
testme after sleep
2007-04-12 21:44:18 DEBUG txn.1090525536 commit <Connection at 2aaab3330110>
2007-04-12 21:44:18 DEBUG txn.1090525536 commit
testme after sleep
2007-04-12 21:44:19 INFO ZPublisher.Conflict ConflictError at /testme:
database conflict error (oid 0x2b, class
Products.faster.sessiondata.SessionDataContainer, serial this txn
started with 0x036ce71f217604aa 2007-04-12 19:43:07.842424, serial
currently committed 0x036ce7204e9b7a44 2007-04-12 19:44:18.423594) (21
conflicts (0 unresolved) since startup at Thu Apr 12 19:55:58 2007)
2007-04-12 21:44:20 DEBUG txn.1098918240 abort
2007-04-12 21:44:20 DEBUG txn.1098918240 new transaction
testme started
testme after sleep
2007-04-12 21:44:20 INFO ZPublisher.Conflict ConflictError at /testme:
database conflict error (oid 0x2b, class
Products.faster.sessiondata.SessionDataContainer, serial this txn
started with 0x036ce71f217604aa 2007-04-12 19:43:07.842424, serial
currently committed 0x036ce7204e9b7a44 2007-04-12 19:44:18.423594) (22
conflicts (0 unresolved) since startup at Thu Apr 12 19:55:58 2007)
2007-04-12 21:44:21 DEBUG txn.1082132832 abort
2007-04-12 21:44:21 DEBUG txn.1082132832 new transaction
testme started
testme after sleep
2007-04-12 21:45:10 DEBUG txn.1098918240 commit <Connection at 2aaab31052d0>
2007-04-12 21:45:10 DEBUG txn.1098918240 commit
testme after sleep
inside of _p_resolveConflict for SessionDataContainer
2007-04-12 21:45:11 DEBUG txn.1082132832 commit <Connection at 2aaab1c75710>
2007-04-12 21:45:11 DEBUG txn.1082132832 commit
(...)


-- 
Maciej Wisniowski
_______________________________________________
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to