Zope 2

Cachemanager duplicates the cache id when copied

Bug #534653 reported by LeoRochael on 2010-03-08

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Zope 2	Fix Released	Medium	Unassigned	Zope 2 2.12.4

Bug Description

When a RAMCacheManager or AcceleratedHTTPCacheManager is copied in the ZMI, its cacheid is not recreated resulting in two different cache managers caching to the same location.

See attached patch that adds a test showing cloned cache managers returning the same cache.

Revision history for this message

LeoRochael (leorochael) wrote on 2010-03-08:

diff adding test for cache behaviour on copy and move Edit (5.1 KiB, text/x-diff)

Revision history for this message

LeoRochael (leorochael) wrote on 2010-03-11:

Fix for duplicate cache ID on copy Edit (8.7 KiB, text/plain)

Attached is another patch with the above test and its solution.

Will commit to Zope 2.12 and trunk in 2 days if no comment is received.

Should other branches receive this fix as well?

Revision history for this message

Tres Seaver (tseaver) wrote on 2010-03-11:

+1 for merging that patch to the 2.12 branch and the trunk.

I don't know if I would bother with earlier branches, unless you have need to support that usecase yourself on an earlier version.

Revision history for this message

LeoRochael (leorochael) wrote on 2010-03-12:

Fix commited to branch 2.12 and trunk

Changed in zope2:
status:	New → Fix Committed

Hanno Schlichting (hannosch) on 2010-04-08

Changed in zope2:
milestone:	none → 2.12.4
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Patches

Fix for duplicate cache ID on copy Edit

Add patch

Bug attachments

diff adding test for cache behaviour on copy and move Edit

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.