First, please stay on the list.
Major releases should be out every 6 month although major releases
will appear as soon as things are done and as soon as we have new code
justifying new major releases. Minor releases will be done either in case
of critical or security related fixes as soon as possible or from time to
time
as needed (as in this case).
Andreas
------------ Forwarded Message ------------
Date: 6. Juni 2007 15:38:21 -0300
From: Fabio Rizzo Matos <fabiorizzo(a)gmail.com>
To: Andreas Jung <lists(a)zopyx.com>
Subject: Re: [Zope-dev] Upcoming Zope releases
Hi Andreas,
I'm owner of a company that work only with Python,Zope and Plone. So, i have
a doubt: How you plan the releases? This information is important for update
my clients and projects.
ps: I'm fan of your work!
Thanks
On 6/6/07, Andreas Jung <lists(a)zopyx.com> wrote:
>
> Hi,
>
> just for your information: I plan to release Zope 2.9.8 and 2.10.4
> around June 24th. Commit your bugs in time.
>
> Cheers,
> Andreas
> _______________________________________________
> Zope-Dev maillist - Zope-Dev(a)zope.org
> 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 )
>
>
>
--
Fabio Rizzo
ThreePointsWeb
fabiorizzo(a)threepointsweb.com
----
---------- End Forwarded Message ----------
--
ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376
Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535
Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK
------------------------------------------------------------------------
E-Publishing, Python, Zope & Plone development, Consulting
Hi,
in our Studentregistration portal we experience many conflict errors
under heavy load many of them unresolved.
the configuration
ZEO-server running on one machine
4 Zope-Clients with CPS-3.4.2 with 4 threads each running on a second
box, we are using the faster session product
all running Zope 2.9.3, python 2.4.3 on Ubuntu 4.0.3
a typical case looks like this:
about 5 or 6 messages in the log file with the oid 0x2b
2007-05-23T17:32:38 INFO ZPublisher.Conflict ConflictError at
/VirtualHostBase/http/uniben.waeup.org:80/uniben/VirtualHostRoot/campus/students/S882364/study_course/create_level:
database conflict error (oid 0x2b, class
Products.faster.sessiondata.SessionDataContainer, serial this txn
started with 0x036dd29c28404f33 2007-05-23 16:28:09.433877, serial
currently committed 0x036dd29ed2491566 2007-05-23 16:30:49.285660) (780
conflicts (73 unresolved) since startup at Wed May 23 05:56:52 2007)
and finally
------
2007-05-23T17:32:38 ERROR Zope.SiteErrorLog
http://uniben.waeup.org/campus/students/S882364/study_course/create_level
Traceback (innermost last):
Module Zope2.App.startup, line 173, in zpublisher_exception_hook
Module ZPublisher.Publish, line 121, in publish
Module Zope2.App.startup, line 240, in commit
Module transaction._manager, line 96, in commit
Module Products.CPSCompat.PatchZODBTransaction, line 175, in commit
Module transaction._transaction, line 433, in _commitResources
Module ZODB.Connection, line 484, in commit
Module ZODB.Connection, line 526, in _commit
Module ZODB.Connection, line 554, in _store_objects
Module tempstorage.TemporaryStorage, line 200, in store
ConflictError: database conflict error (oid 0x2b, class
Products.faster.sessiondata.SessionDataContainer, serial this txn
started with 0x036dd29c28404f33 2007-05-23 16:28:09.433877, serial
currently committed 0x036dd29ed2491566 2007-05-23 16:30:49.285660)
Even though we have many write operations the write operations can't
actually conflict, since each student only works on his own documents.
Any hints howto to get further insight into this problem is welcome.
--
Gruß Joachim
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jürgen Kartnaller wrote:
> We also run into this kind of problems.
>
> The only save way to solve it was to serialize our index updates.
>
> We do this by using one zope instance which runs only a
> lovely.remotetask task service. This service contains an indexing task.
> When indexing is needed we just create a new indexing job which is
> stored in the job list of the remote task service.
That is exactly how QueueCatalog functions: it "batches" expensive /
conflict-prone indexing operations into jobs which are handled later, in
a serialized way.
> This solves two problems :
>
> - conflicts
> - low speed because of complex index value calculations
>
> Btw the setup for this application contains 18 zope's each zope running
> one thread. 17 zope's are used to handle browser requests and one is
> used to handle the remote tasks (not only indexing tasks).
How many of the front-end servers do writes? Or are all your visitors
potential writers?
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver(a)palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGYOWr+gerLs4ltQ4RAmpyAJwPxdx+ob46RgvasStZwoPWQQTa8gCdG/+t
05J+ocnTgZVOnf7MvLw3oGw=
=kyUn
-----END PGP SIGNATURE-----