Chris McDonough wrote: >On Thu, 2005-04-14 at 14:42, Jean-Marc Orliaguet wrote: > > > >>we are also experiencing an abnormal number of conflict errors on >>objects where there is not supposed to be any write access (such as >>skins, DTML documents) >> >>2005-04-14T19:55:01 INFO(0) ZODB conflict error at >>/VirtualHostBase/http/xxx.xxx.xxx:80/chalmers-en/VirtualHostRoot/_vh_en/forum.css >>(416 conflicts since startup at 2005-04-11T08:10:22) >> >>2005-03-20T19:00:43 INFO(0) ZODB conflict error at >>/VirtualHostBase/https/xxx.xxx.xxx:443/VirtualHostRoot//chalmers-sv/sections/.heartbeat.txt >>(1129 conflicts since startup at 2005-03-07T17:08:38) >> >>Zope-2.7.4 / ZEO / CMF 1.4.7 >> >> > >Are you using session-based authentication by any chance? > >- C > >
these are unauthenticated pages that cause conflict errors, otherwise authentication uses a cookie to store the ZopeID, and everything else that has to do with authenticated user information (user id basically) is stored in a RAM cache. a new session ZopeID is generated for every individual browser hit though. .... HTTP request sent, awaiting response... 1 HTTP/1.1 200 OK 2 Date: Thu, 14 Apr 2005 19:51:20 GMT 3 Server: Zope/(Zope 2.7.4-1, python 2.3.4, linux2) ZServer/1.1 CPS/3.2 4 Content-Length: 16795 5 Content-Type: text/html; charset=ISO-8859-15 6 Set-Cookie: _ZopeId="41473498A1yZZ1hSqjM"; Path=/ 7 Connection: close /JM _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests