[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph reopened MAGNOLIA-3860:
--------------------------------------


There was indeed no reason to close this, the issue still exists.

> CacheModuleLifecycleListener references are not deleted on cache module 
> restart
> -------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-3860
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3860
>             Project: Magnolia
>          Issue Type: Bug
>      Security Level: Public
>          Components: cache
>    Affects Versions: 4.4.4
>            Reporter: Stefan Baur
>            Priority: Major
>
> I have a class listening to the cache module startup event like:
> CacheModule.getInstance().register(new CacheModuleLifecycleListener() {
>             public void onCacheModuleStart() {
>                doStuff();
>             }
> });
> If a cache module reload is triggered (by changing content in the cache 
> config), doStuff() will be called twice, and after again triggering a reload, 
> doStuff() will be called three times.
> I could work around this by overriding hashCode() and equals() in my 
> CacheModuleLifecycleListener, but thought this could be fixed anyway.
> Will it need a reset of the listeners Map in 
> info.magnolia.module.cache.CacheModule#stop ?
> Regards,
> Stefan

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       


----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to