JobExecutor
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2010 04:19 AM
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?
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?
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2010 04:31 AM
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?
Is there a reason that we would want to have the job executor *not* activated while Activiti is running?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2010 09:52 AM
For performance reasons, when you don't have processes that have timers or other jobs 🙂
