Hey guys, thanks for the replies and hints. I finally realized that the problem was indeed in the PersistenceManager. The way it was handling the bundles was wrong even when multiple PMs were pointing to the same persistence location (db url).
Keep on the good work! Cheers. On Wed, Sep 29, 2010 at 7:42 PM, Alexander Klimetschek <[email protected]>wrote: > On Wed, Sep 29, 2010 at 15:18, William Ribeiro <[email protected]> > wrote: > > Okay ... this what I got so far! What am I missing??? I didn't see the > new > > changes being stored by the PersistenceManager. I'm stuck with this for > > almost 1 week now! > > Again: the cluster node that receives an update through the journal > only has to invalidate its caches. The actual node/property data > clustering must happen in the persistence manager, so that the next > time the application on the other cluster node reads such an updated > node, will get the latest version from the persistence manager. > > Regards, > Alex > > -- > Alexander Klimetschek > [email protected] > -- Met vriendelijke groet, Tricode Professional Services BV William R. J. Ribeiro Developer T: +31 (0)318 55 92 10 F: +31 (0)318 65 09 09 E: [email protected] W: www.tricode.nl De Schutterij 12, 3905 PL Veenendaal, The Netherlands | KVK 30183142
