nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

JobExecutor

turgayz

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?

Find more posts tagged with

Comments

turgayz

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

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