ZEO connections cache
Hi, I am using Zope 2.7.3 with this configuration : + a ZEO instance with one ZODB + a Zope instance with Read/Write connections to the whole ZEO ZODB + several Zope instances with Read Only connections to one folder of the ZEO ZODB (+ a small local ZODB for the root folder, that never changes) It looks like some object changes (specially objects located in CMF portal_skins subfolders), are not always "seen" from one connection to another (either on the Zope instance where the changes were made or any other Zope instance). The problem is fixed when I minimize the connection caches. Anyone knows what could cause such an issue ? It appeared with Zope 2.7.3... (was ok on 2.7.2) But as we did other changes at the same time, I am 100% sure it's because of the Zope upgrade itself. Thanks a lot. Pascal ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************
Pascal Peregrina wrote:
Hi,
I am using Zope 2.7.3 with this configuration : + a ZEO instance with one ZODB + a Zope instance with Read/Write connections to the whole ZEO ZODB + several Zope instances with Read Only connections to one folder of the ZEO ZODB (+ a small local ZODB for the root folder, that never changes)
It looks like some object changes (specially objects located in CMF portal_skins subfolders), are not always "seen" from one connection to another (either on the Zope instance where the changes were made or any other Zope instance).
The problem is fixed when I minimize the connection caches.
Anyone knows what could cause such an issue ?
It appeared with Zope 2.7.3... (was ok on 2.7.2) But as we did other changes at the same time, I am 100% sure it's because of the Zope upgrade itself.
Are the modified objects ZODB-based skin methods, or the filesystem-based analogs in a FilesystemDirectoryView? I don't know of anything which would explain your behavior for ZODB-based objects; such staleness would imply a bug in ZODB invalidation logic. FSObject-derived items have a "proxy" stored in the ZODB, which caches the "real" method object as a volatile attribute; cache minimization would cause those volatiles to be discarded and recomputed, and might therefore contribute to the behavior you describe. Tres. -- =============================================================== Tres Seaver tseaver@zope.com Zope Corporation "Zope Dealers" http://www.zope.com
Pascal Peregrina wrote at 2005-1-6 17:23 +0100:
I am using Zope 2.7.3 with this configuration : + a ZEO instance with one ZODB + a Zope instance with Read/Write connections to the whole ZEO ZODB + several Zope instances with Read Only connections to one folder of the ZEO ZODB (+ a small local ZODB for the root folder, that never changes)
It looks like some object changes (specially objects located in CMF portal_skins subfolders), are not always "seen" from one connection to another (either on the Zope instance where the changes were made or any other Zope instance).
Maybe, a bug with "read only" connections? Try to switch to all "read/write" connections and see whether the problem disappears. -- Dieter
participants (3)
-
Dieter Maurer -
Pascal Peregrina -
Tres Seaver