The problem is related to URL structure and the fact that the suffix for
the original resource
does not have any extension. Dispatcher ignores such requests. Sadly, It
looks like a dead end... However, with a bit of trick you can force the
dispatcher to cache it. If you name your contexthub configuration in a
way which ends with an extension, i.e.
/conf/xxx/settings/cloudsettings/default/contexthub.js, then the ful...
I've had the same problem. It looks like standby sync got broken in
oak-segment-tar 1.22.9 (available in SP11) or even earlier version and
then fixed in 1.22.10. Because of an earlier change in how the config
was handled, int property could not be casted into long and the
synchronization jobs were never run on AEM Standby instance. Therefore,
JMX showed the Standby process as "Initializing". This problem is
visible in logs too:13.10.2021 16:29:41.575 *WARN* [CM Event Dispatcher