it was a very bad fix, and makes the query release strategies impossible. I think the problem lies with the SharedStorage class. it's a bit fuzzy to me, but that class (called by the ChangeManager) should notify the local listening builders of occuring changes (like MMBaseChangeDummy dous). It dous not do so directly, but creates a message that goes into the que. i suppose at some point (after the message is sent?) local listeners are notified, which might well be too late. I think we can solve this problem while we rework the multicast implementation for the event model. I am preparing an email to propose a meeting for this.
Ernst > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Michiel Meeuwissen > Verzonden: vrijdag 16 september 2005 10:30 > Aan: [email protected]; [EMAIL PROTECTED] > Onderwerp: [Developers] Re: [MMBASE CVS] > src/org/mmbase/module/coreMMObjectBuilder.java > > > Ernst Bunders wrote: > > // that imediate 'select' after 'insert' will be correct'. > > - QueryResultCache.invalidateAll(this); > > + //xxx: this is bad.let's kill it! > > + //QueryResultCache.invalidateAll(this); > > I think this was the fix for bug #6348; I suppose it is back > now. If it is bad, which I'm ready to assume, then an > alternative fix must be deviced. > > Michiel > > > > -- > Michiel Meeuwissen mihxil' > Peperbus 111 MediaPark H'sum [] () > +31 (0)35 6772979 nl_NL eo_XX en_US > > > > _______________________________________________ > Developers mailing list > [email protected] > http://lists.mmbase.org/mailman/listinfo/developers > _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
