Scheduler tasks and J2EE context

 

When a task is created using the Scheduler API create() method, the J2EE thread context of the creator is stored with the scheduled task. When the task runs, the original J2EE thread context is reapplied to the thread before calling the customer TaskInfo instance.

The scheduler service utilizes the asynchronous beans deferred start mechanism to propagate J2EE service context information to a task when it runs. The amount of service context information that is propagated is controlled by the Service Context settings on the WorkManager configuration object that schedulers reference. For example, security and internationalization service contexts can be enabled. See Use asynchronous beans for details on how to configure the Application Server to propagate these service contexts.

---

Sub-topics

Transactions and schedulers

Scheduler task user authorization

 

Related tasks

Securing scheduler tasks
Use asynchronous beans