On Fri, Sep 28, 2012 at 10:03 AM, Paul Libbrecht <paul(a)hoplahup.net> wrote:
Thank you Thomas,
so it turned out an elementary configuration bit caused the test with titles to fail: the
presence of a cache folder in WEB-INF containing various cache configs. Removing that
made the test with titles and contents succeed.
However, the test with collections still fails, and now I finally had it to fail on my
sever as well: two tomcats, joined through a tcp channel, ... What I observe is that after
a revision is cached in a server, a change of objects only on the other does not
propagate. The event and history frame comes up, not the added object.
Let me understand: jgroups just does the communication, and listeners include a cache
listener which invalidate the entry when the document-event is fired.
Is it correct?
Yes.
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…).
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. 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.
thanks in advance
Paul
--
Thomas Mortagne