have you tried to invoke the start script from your dockerfile instead of invoking the JAR directly?

Is this AEM Cloud Service? In that case you cannot bypass the CDN from an external endpoint (for security reasons), and therefor you are unable to connect to the origin endpoints (which the CDN itself is connecting to).

This does not work, the cq:page nodetype is pretty much locked down what additional properties you can add to it. cq:lastReplicated is always set on the jcr:content node. (Plus: on a publish instance it is not reliable, because this property is only set on author after the replication has completed....

Congratulations @arunpatidar! That recognition is well deserved!

It seems that you want to override the exporter for the v3 page template of the Core Components. And most likely there is already one for it, and for that reason it's not working. I would recommend that you define for your own pages a dedicated resourcetype (you can define the v3 page as supertype) ...

Well, for me that feels like a bandaid for a different problem...

Why don't you use the replication API for this? 

The dispatcher is not involved here, this error message comes from AEM directly.

I wrote a 2 blog posts in the context of AEM CS backups and how you should use them: AEM CS backups are not for archival. And in my blog post I raised a number of questions why in one of my consulting projects I did not considered backups as a proper solution for an AEM on prem setup.And most of the...

What type of event listener do you use? JCR Observation listener or Sling ResourceChange listener? And can you share the event handler you implemented?