The "concurrency" flag of the Sling Scheduler just relates to the very
same instance. Assuming that you want to start a job every 5 seconds and
it normally takes just 1 second, but sometimes it takes longer. In that
case the "concurrency" flag controles if the scheduler should start a
new instance of the scheduled job after 5 seconds, no matter if the
previous execution has been finished.
Thanks for the reply. With cloud aem, our dispatcher configs only have
http. We assume that the cloud has some sort of https termination
infront of the dispatcher (WAF may be). The crux is that our vhosts for
cloud have not https config (that we know of), and we cant modify them
or it will break production. Any suggestions?
Hi, Yes, I have followed this article, but validate.sh tries to start a
docker instance, but there are no instructions how to create the docker
image it needs. I tried creating one manually, but I can't find any
Dockerfile. This seems to be a critical gap in the documentation - you
cant run the local dispatcher or validator without a docker image, but
to create a docker image you need a Dockerfile which specifies what the
image contains, and this appears to be missing from the dispatcher tools
That explanation is technically correct, but I just want to give some
more context. In this case the order matters. If a request comes in and
the correct vhost is about to determined, a "ServerAlias *" is a
catch-all definition, and it will be used. So you should make sure that
this definition is the last one to be loaded. More specific vhosts
should be loaded before. So you can try to rename the "default.vhost" to
"999_default.vhost" (alphabetical order matters here) and try again.
Would love t...
When I run: docker build --platform linux/amd64 -t simon-dispatcher-vm I
get unable to prepare context: unable to evaluate symlinks in Dockerfile
path: lstat /Users/me/dev/docker/Dockerfile: no such file or directory
where does one get the Dockerfile?