[ 
https://issues.apache.org/jira/browse/COCOON-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546223
 ] 

Ard Schrijvers commented on COCOON-2152:
----------------------------------------

Since you found the problem my comment from COCOON-2146 can be discarded.  I 
merely stated there that for  < 2.1.8  cocoon versions it used to work. Since 
we have our own implementation for it, I wasn't aware that it actually changed. 
Anyway, good to know you found the problem!

> EventAware cache does not persist correctly when using the 
> StoreEventRegistryImpl
> ---------------------------------------------------------------------------------
>
>                 Key: COCOON-2152
>                 URL: https://issues.apache.org/jira/browse/COCOON-2152
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Event Cache
>    Affects Versions: 2.1.10, 2.1.11-dev (Current SVN), 2.2-dev (Current SVN)
>            Reporter: Ellis Pritchard
>
> 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 TO DISK BY 
> EHCACHE SHUTDOWN!
> 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.

Reply via email to