28 Sep
2012
28 Sep
'12
12:20 p.m.
On Fri, Sep 28, 2012 at 12:02 PM, Paul Libbrecht <paul(a)hoplahup.net> wrote:
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
Indeed.
The first
thing to make sure is to check of JGroups message go from
one server to another both way, you can enable remote observation
module debug log for this (see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Observation+Module+Rem…).
Done and checked: yes it works.
(all written down on http://jira.xwiki.org/browse/CURRIKI-5909)
There is several caches in XWiki and you maybe
have several of your
own so if jgroups properly send messages it mean some cache somewhere
corresponding to what you are viewing is not invalidated when
receiving an event.
Can it be it's invalidated too early?
This seems to be my best guess.
Then the older version is fetched from the DB. 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#HXWikiCaches…),
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?
paul
--
Thomas Mortagne