Hi everyone, I would like to start the Job Executor after we have ensured that all the components are ready.
I tried setting jobExecutorActivate to ‘false’, so I can start it in a later event:
public class ProcessEngineConfig extends AbstractProcessEnginePlugin {
@Override
public void preInit(ProcessEngineConfigurationImpl processEngineConfiguration) {
processEngineConfiguration.setJobExecutorActivate(false);
}
}
This has stopped the Job Executor from activating immediately after Process Engine has started.
However, the Job Executor is still getting started by itself when it receives the ApplicationReadyEvent.
The ApplicationReadyEvent seems to have activated the Job Executor in JobExecutorStartingEventListener
that is listening to ProcessApplicationStartedEvent
, which is being injected in DefaultJobConfiguration
(https://github.com/camunda/camunda-bpm-spring-boot-starter/blob/master/starter/src/main/java/org/camunda/bpm/spring/boot/starter/configuration/impl/DefaultJobConfiguration.java#L124).
Is this the expected behaviour? Or am I missing something?
Thank you!