So it appears that the bug was solved by adjusting our notification listener to ignore notifications when a LazyXWikiDocument is used. This prevents the LazyXWikiDocument to be put in the cache.
This does not seems documented but I seem to observe that LazyXWikiDocument is in notifications when that notification is coming from outside. Do I have another way to recognize it? thanks in advance Paul > It should not, a document event for example is send after the document > is saved in the database so if you react to this event you can't > invalidate the cache too early. > > IMO there is only two possibilities here: > * the listener that is supposed to invalidate the cache does not > receive the event for some reason > * there is no such listener or it's buggy > >> >>> When you can reproduce the issue the idea would be to find what is the >>> cache with the issue, it's not always easy to find out when you don't know >>> exactly all the caches but you can view all of >>> them using JMX (see >>> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Monitoring#HXWikiCachesMonitoring), >>> at least all the caches created through standard XWiki cache module. >> >> Thus far, any such inconsistency, on production environments, is solved with >> a cache-clear so this is likely. >> >> I could find out by just emptying one or the other right? > > Indeed. > >> >> paul > > > > -- > Thomas Mortagne > _______________________________________________ > xclams-devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/xclams-devs _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
