Simon Groenewolt wrote:
hi Ernst,
Ernst Bunders wrote:
I did check cloud hash codes, and they are the same. also when I
lookup node 107 in the editor the lastposternumber is empty, as you
should expect.
does anybody have any ideas at all? It would be nice, because i'm out
at the moment.
A wild guess: did you check the caching code in mmbob?
Well, mmbob caches objects that more or less wrap mmbase nodes. When these
objects are modified they are added to a que that periodically updates every
node that is represented by the objects in it.
From this perspective the procedure of removing all the references of posters
and postings in various nodes is actually wrong, because the reference is not
removed from the 'wrapping ' object (in this case a
org.mmbase.applications.mmbob.PostArea instance). So, if this object should
happen to be in the que awaiting an update to the database, and:
1) the mmbase node is modified by removing the poster
2) the que recommits the node with the values of the wrapping object
3) the mmbase node is modified by removing the posting
then you would get exactly the bug that i'm getting.
the problem is that i don't see this happening.
But the caching of these wrapper objects and the update ques are definitely a
concern, and maybe i have to look at it a little harder yet.
regards,
Ernst
Simon
PS: removed 'r' from subject line ;-)
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
