When updating a collection that is in the ReadWriteCache,
the collection is never unlocked from the cache. This causes subsequent
requests after an update to hit the database again. It is my
understanding that items in the ReadWriteCache should not be invalidated from
the cache when the object is flushed. If this is correct then here is a
patch that updates the collection in the cache the same way that entities are
updated. Would have posted to jira but its down.
Jesse
Attachment: CollectionAction_unlock.patch (zipped)