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

Cédric Damioli commented on COCOON-2152:
----------------------------------------

the preceding comment suggests that the problem is to be fixed in 2.2.x, not in 
2.1.x
I then remove the "fix-for 2.1.12" tag
                
> 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, 2.2
>            Reporter: Ellis Pritchard
>            Assignee: Andrew Savory
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to