[ZCM] [ZC] 2231/ 3 Comment "ZODB Cache on manual refresh"
"Collector: Zope Bugs, Features, and Patches ..." <[email protected]> Wed, 14 Feb 2007 04:33:27 -0500
| Newsgroups | gmane.comp.web.zope.devel.collector-monitor |
|---|---|
| Message-ID | <[email protected]> |
Issue #2231 Update (Comment) "ZODB Cache on manual refresh" Status Pending, Zope/bug medium To followup, visit: http://www.zope.org/Collectors/Zope/2231 ============================================================== = Comment - Entry #3 by pjstevns on Feb 14, 2007 4:33 am Any updates on this bug? We're seeing this quite a lot on our zope2.9 development instances, making 2.9 almost unusable as a developement platform. Please see ticket 5615 on the plone collector for some of the impact this bug has: https://dev.plone.org/plone/ticket/5615 ________________________________________ = Edit - Entry #2 by ajung on Nov 12, 2006 3:21 am Changes: submitter email, importance (critical => medium) ________________________________________ = Request - Entry #1 by burbank on Nov 3, 2006 4:48 pm After manually refreshing a Product and the trying to create new instance of a content type from that Product, I get a an error. The trace is listed below. Refresh is a very compelling part of Zope and Plone development for myself and other developers, so any assistance is very much appreciated. Thank you. 2006-11-03T13:28:35 ERROR Zope.SiteErrorLog http://XXX.XXX.XXX.XXX:8088/FSCVL/FSCVL/test/portal_factory/Training Event/training_event.2006-11-03.3081931765/base_edit Traceback (innermost last): Module ZPublisher.Publish, line 121, in publish Module Zope2.App.startup, line 240, in commit Module transaction._manager, line 96, in commit Module transaction._transaction, line 380, in commit Module transaction._transaction, line 378, 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 560, in _store_objects ValueError: Cache values may only be in one cache. ==============================================================