类 ExecutorConfigurationSupport

java.lang.Object
cn.taketoday.util.CustomizableThreadCreator
cn.taketoday.scheduling.concurrent.CustomizableThreadFactory
cn.taketoday.scheduling.concurrent.ExecutorConfigurationSupport
所有已实现的接口:
Aware, BeanNameAware, DisposableBean, InitializingBean, Serializable, ThreadFactory
直接已知子类:
ScheduledExecutorFactoryBean, ThreadPoolExecutorFactoryBean, ThreadPoolTaskExecutor, ThreadPoolTaskScheduler

public abstract class ExecutorConfigurationSupport extends CustomizableThreadFactory implements BeanNameAware, InitializingBean, DisposableBean
Base class for setting up a ExecutorService (typically a ThreadPoolExecutor or ScheduledThreadPoolExecutor). Defines common configuration settings and common lifecycle handling.
从以下版本开始:
4.0
作者:
Juergen Hoeller
另请参阅:
  • 字段详细资料

    • logger

      protected final cn.taketoday.logging.Logger logger
  • 构造器详细资料

    • ExecutorConfigurationSupport

      public ExecutorConfigurationSupport()
  • 方法详细资料

    • setThreadFactory

      public void setThreadFactory(@Nullable ThreadFactory threadFactory)
      Set the ThreadFactory to use for the ExecutorService's thread pool. Default is the underlying ExecutorService's default thread factory.

      In a Jakarta EE or other managed environment with JSR-236 support, consider specifying a JNDI-located ManagedThreadFactory: by default, to be found at "java:comp/DefaultManagedThreadFactory". Use the "jee:jndi-lookup" namespace element in XML or the programmatic JndiLocatorDelegate for convenient lookup. Alternatively, consider using DefaultManagedAwareThreadFactory with its fallback to local threads in case of no managed thread factory found.

      另请参阅:
    • setThreadNamePrefix

      public void setThreadNamePrefix(@Nullable String threadNamePrefix)
      覆盖:
      setThreadNamePrefix 在类中 cn.taketoday.util.CustomizableThreadCreator
    • setRejectedExecutionHandler

      public void setRejectedExecutionHandler(@Nullable RejectedExecutionHandler rejectedExecutionHandler)
      Set the RejectedExecutionHandler to use for the ExecutorService. Default is the ExecutorService's default abort policy.
      另请参阅:
    • setWaitForTasksToCompleteOnShutdown

      public void setWaitForTasksToCompleteOnShutdown(boolean waitForJobsToCompleteOnShutdown)
      Set whether to wait for scheduled tasks to complete on shutdown, not interrupting running tasks and executing all tasks in the queue.

      Default is "false", shutting down immediately through interrupting ongoing tasks and clearing the queue. Switch this flag to "true" if you prefer fully completed tasks at the expense of a longer shutdown phase.

      Note that container shutdown continues while ongoing tasks are being completed. If you want this executor to block and wait for the termination of tasks before the rest of the container continues to shut down - e.g. in order to keep up other resources that your tasks may need -, set the "awaitTerminationSeconds" property instead of or in addition to this property.

      另请参阅:
    • setAwaitTerminationSeconds

      public void setAwaitTerminationSeconds(int awaitTerminationSeconds)
      Set the maximum number of seconds that this executor is supposed to block on shutdown in order to wait for remaining tasks to complete their execution before the rest of the container continues to shut down. This is particularly useful if your remaining tasks are likely to need access to other resources that are also managed by the container.

      By default, this executor won't wait for the termination of tasks at all. It will either shut down immediately, interrupting ongoing tasks and clearing the remaining task queue - or, if the "waitForTasksToCompleteOnShutdown" flag has been set to true, it will continue to fully execute all ongoing tasks as well as all remaining tasks in the queue, in parallel to the rest of the container shutting down.

      In either case, if you specify an await-termination period using this property, this executor will wait for the given time (max) for the termination of tasks. As a rule of thumb, specify a significantly higher timeout here if you set "waitForTasksToCompleteOnShutdown" to true at the same time, since all remaining tasks in the queue will still get executed - in contrast to the default shutdown behavior where it's just about waiting for currently executing tasks that aren't reacting to thread interruption.

      另请参阅:
    • setAwaitTerminationMillis

      public void setAwaitTerminationMillis(long awaitTerminationMillis)
      Variant of setAwaitTerminationSeconds(int) with millisecond precision.
      另请参阅:
    • setBeanName

      public void setBeanName(String name)
      指定者:
      setBeanName 在接口中 BeanNameAware
    • afterPropertiesSet

      public void afterPropertiesSet()
      Calls initialize() after the container applied all property values.
      指定者:
      afterPropertiesSet 在接口中 InitializingBean
      另请参阅:
    • initialize

      public void initialize()
      Set up the ExecutorService.
    • initializeExecutor

      protected abstract ExecutorService initializeExecutor(ThreadFactory threadFactory, RejectedExecutionHandler rejectedExecutionHandler)
      Create the target ExecutorService instance. Called by afterPropertiesSet.
      参数:
      threadFactory - the ThreadFactory to use
      rejectedExecutionHandler - the RejectedExecutionHandler to use
      返回:
      a new ExecutorService instance
      另请参阅:
    • destroy

      public void destroy()
      Calls shutdown when the BeanFactory destroys the task executor instance.
      指定者:
      destroy 在接口中 DisposableBean
      另请参阅:
    • shutdown

      public void shutdown()
      Perform a shutdown on the underlying ExecutorService.
      另请参阅:
    • cancelRemainingTask

      protected void cancelRemainingTask(Runnable task)
      Cancel the given remaining task which never commended execution, as returned from ExecutorService.shutdownNow().
      参数:
      task - the task to cancel (typically a RunnableFuture)
      另请参阅: