cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Savory (JIRA)" <>
Subject [jira] Closed: (COCOON-2152) EventAware cache does not persist correctly when using the StoreEventRegistryImpl
Date Mon, 02 Jun 2008 13:53:45 GMT


Andrew Savory closed COCOON-2152.

       Resolution: Fixed
    Fix Version/s: 2.1.12-dev (Current SVN)

Fixed in SVN. Patch from Ellis applied, and a separate fix for samples added.

> EventAware cache does not persist correctly when using the StoreEventRegistryImpl
> ---------------------------------------------------------------------------------
>                 Key: COCOON-2152
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Event Cache
>    Affects Versions: 2.1.10, 2.1.11, 2.2
>            Reporter: Ellis Pritchard
>            Assignee: Andrew Savory
>             Fix For: 2.1.12-dev (Current SVN)
> When using the DefaultEventRegistryImpl the functionality now works as expected (events
are persisted and restored) after the patch applied in COCOON-2146.
> However, there's still a problem with StoreEventRegistryImpl.
> The behaviour is that it doesn't seem to actually write/restore any event entries: the
maps in the EventRegistryDataWrapper are empty (but not null) after restart, even though the
actual cache entry (key EVENTREGWRAPPER) was found in the Store, and the entries were present
when persist() was called.
> The effect of this is to correctly restore the cached entries, but discard all the events,
which means that event-flushes don't work any more, which is not a good thing.
> I've tracked this down to the fact that AbstractDoubleMapEventRepository#dispose() which
performs the persist(), then immediately clear()s the maps, WHICH HAVEN'T YET BEEN WRITTEN
> This code has probably never worked :)
> Patches to follow; I propose modifying dispose() to null the map fields, but not perform
clear() on them.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message