Assuming these are in the same JVM, I think what you're looking for is peer context synchronization. This is disabled by default (but might have been on by default previously). Wherever you create your ServerRuntime you can add this:
binder.bindMap(Boolean.class, Constants.PROPERTIES_MAP).put(Constants.SERVER_CONTEXTS_SYNC_PROPERTY, true); It is discouraged as synchronizing all contexts is a heavy operation (even though it is done asynchronously). I would love a feature where I could choose which contexts I care about synchronization (like think within a given web session), but I've learned to live without it. Be well, Lon On Sun, Dec 20, 2020 at 12:13 AM Millinger Ernst <ernst.millin...@egger.com> wrote: > Hello everyone, > > Since updating Cayenne from Version 4.0.M2 to 4.1 I face the following > problem (which worked out o.k. before): > > If I start the same web application within the same server twice and > modify data in the first application, the changes are not propagated to the > second application although fetching the modified object from the DB again. > "Use Shared Cache" is activated on the Data Node. > When invalidating the object, changes are visible, but I think this should > work implicitly. > > Have there been any changes triggering this event? If so, how can I > activate it again? > > Thank you in advance, > BR, > Ernst >
