cancel
Showing results for 
Search instead for 
Did you mean: 

JobExecutor

turgayz
Champ in-the-making
Champ in-the-making
Hi,
In BoundaryTimerEventTest, there is a JobExecutor instance started, and then shutdown at the end of the test.

I understand that the JobExecutor is not started by the engine at startup. This means we must start/stop it manually. Will this change in the future?
2 REPLIES 2

turgayz
Champ in-the-making
Champ in-the-making
OK, I saw in the User Guide that "job.executor.auto.activate=off needs to be removed from the activiti.properties" so please ignore the original question.
Is there a reason that we would want to have the job executor *not* activated while Activiti is running?

jbarrez
Star Contributor
Star Contributor
For performance reasons, when you don't have processes that have timers or other jobs 🙂