C# Class BitSharper.Threading.Execution.ThreadPoolExecutor

Blocks until all tasks have completed execution after a shutdown request, or the timeout occurs, or the current thread is interrupted, whichever happens first.

Shutsdown and disposes of this ThreadPoolExecutor.

Starts all core threads, causing them to idly wait for work.

This overrides the default policy of starting core threads only when new tasks are executed.

Starts a core thread, causing it to idly wait for work. This overrides the default policy of starting core threads only when new tasks are executed. This method will return false if all core threads have already been started.

Tries to remove from the work queue all IFuture{T} tasks that have been cancelled. This method can be useful as a storage reclamation operation, that has no other impact on functionality. Cancelled tasks are never executed, but may accumulate in work queues until worker threads can actively remove them. Invoking this method instead tries to remove them now. However, this method may fail to remove tasks in the presence of interference by other threads.

Removes this task from the executor's internal queue if it is present, thus causing it not to be run if it has not already started.

This method may be useful as one part of a cancellation scheme. It may fail to remove tasks that have been converted into other forms before being placed on the internal queue. For example, a task entered using IExecutorService.Submit(Action) might be converted into a form that maintains IFuture{T} status. However, in such cases, method Purge may be used to remove those Futures that have been cancelled.

Removes this task from the executor's internal queue if it is present, thus causing it not to be run if it has not already started.

This method may be useful as one part of a cancellation scheme. It may fail to remove tasks that have been converted into other forms before being placed on the internal queue. For example, a task entered using IExecutorService.Submit(Action) might be converted into a form that maintains IFuture{T} status. However, in such cases, method Purge may be used to remove those Futures that have been cancelled.

Initiates an orderly shutdown in which previously submitted tasks are executed, but no new tasks will be accepted. Invocation has no additional effect if already shut down.

Attempts to stop all actively executing tasks, halts the processing of waiting tasks, and returns a list of the tasks that were awaiting execution. These tasks are drained (removed) from the task queue upon return from this method.

There are no guarantees beyond best-effort attempts to stop processing actively executing tasks. This implementation cancels tasks via Thread.Interrupt, so any task that fails to respond to interrupts may never terminate.

Creates a new ThreadPoolExecutor with the given initial parameters and default thread factory and rejected execution handler.

> It may be more convenient to use one of the Executors factory methods instead of this general purpose constructor.

Creates a new ThreadPoolExecutor with the given initial parameters and IThreadFactory.

Creates a new ThreadPoolExecutor with the given initial parameters and default RejectedExecutionException.

Creates a new ThreadPoolExecutor with the given initial parameters and default RejectedExecutionException.

Creates a new ThreadPoolExecutor with the given initial parameters.

Method invoked upon completion of execution of the given Runnable. This method is invoked by the thread that executed the task. If non-null, the exception is the unhandle exception that caused execution to terminate abruptly.

This implementation does nothing, but may be customized in subclasses. Note: To properly nest multiple overridings, subclasses should generally invoke base.AfterExecute at the beginning of this method.

Note: When actions are enclosed in tasks (such as FutureTask{T}) either explicitly or via methods such as IExecutorService.Submit(System.Action), these task objects catch and maintain computational exceptions, and so they do not cause abrupt termination, and the internal exceptions are not passed to this method. If you would like to trap both kinds of failures in this method, you can further probe for such cases, as in this sample subclass that prints either the direct cause or the underlying exception if a task has been aborted:

Method invoked prior to executing the given IRunnable in the given thread.

This method is invoked by thread that will execute runnable, and may be used to re-initialize ThreadLocals, or to perform logging. This implementation does nothing, but may be customized in subclasses. Note: To properly nest multiple overridings, subclasses should generally invoke base.BeforeExecute at the end of this method.

Helper method to dispose of this ThreadPoolExecutor

Executes the given task sometime in the future. The task may execute in a new thread or in an existing pooled thread.

If the task cannot be submitted for execution, either because this executor has been shutdown or because its capacity has been reached, the task is handled by the current IRejectedExecutionHandler for this ThreadPoolExecutor.

Performs any further cleanup following run state transition on invocation of shutdown. A no-op here, but used by ScheduledThreadPoolExecutor to cancel delayed tasks.

Method invoked when the IExecutor has terminated. Default implementation does nothing.

Note: To properly nest multiple overridings, subclasses should generally invoke base.terminated within this method.

Checks if a new worker can be added with respect to current pool state and the given bound (either core or maximum). If so, the worker count is adjusted accordingly, and, if possible, a new worker is created and started running firstTask as its first task. This method returns false if the pool is stopped or eligible to shut down. It also returns false if the thread factory fails to create a thread when asked, which requires a backout of workerCount, and a recheck for termination, in case the existence of this worker was holding up termination.

Transitions control state to given target or leaves if alone if already at least the given target.

Ensures that unless the pool is stopping, the current thread does not have its interrupt set. This requires a double-check of state in case the interrupt was cleared concurrently with a shutdownNow -- if so, the interrupt is re-enabled.

Attempt to CAS-decrement the workerCount field of control state.

Attempt to CAS-increment the workerCount field of control state.

Decrements the workerCount field of ctl. This is called only on abrupt termination of a thread (see ProcessWorkerExit). Other decrements are performed within GetTask.

Drains the task queue into a new list, normally using drainTo. But if the queue is a DelayQueue or any other kind of queue for which poll or drainTo may fail to remove some elements, it deletes them one by one.

Performs blocking or timed wait for a task, depending on current configuration settings, or returns null if this worker must exit because of any of: 1. There are more than maximumPoolSize workers (due to a call to setMaximumPoolSize). 2. The pool is stopped. 3. The pool is shutdown and the queue is empty. 4. This worker timed out waiting for a task, and timed-out workers are subject to termination (that is, allowCoreThreadTimeOut || workerCount > corePoolSize) both before and after the timed wait.

Interrupts all threads that might be waiting for tasks.

Interrupts threads that might be waiting for tasks (as indicated by not being locked) so they can check for termination or configuration changes. Ignores SecurityExceptions (in which case some threads may remain uninterrupted). @param onlyOne If true, interrupt at most one worker. This is called only from TryTerminate when termination is otherwise enabled but there are still other workers. In this case, at most one waiting worker is interrupted to propagate shutdown signals in case all threads are currently waiting. Interrupting any arbitrary thread ensures that newly arriving workers since shutdown began will also eventually exit. To guarantee eventual termination, it suffices to always interrupt only one idle worker, but shutdown() interrupts all idle workers so that redundant workers exit promptly, not waiting for a straggler task to finish.

Interrupts all threads, even if active. Ignores SecurityExceptions (in which case some threads may remain uninterrupted).

State check needed by ScheduledThreadPoolExecutor to enable running tasks during shutdown.

Performs cleanup and bookkeeping for a dying worker. Called only from worker threads. Unless completedAbruptly is set, assumes that workerCount has already been adjusted to account for exit. This method removes thread from worker set, and possibly terminates the pool or replaces the worker if either it exited due to user task exception or if fewer than corePoolSize workers are running or queue is non-empty but there are no workers. the worker if the worker died to the user exception

Invokes the rejected execution handler for the given command.

Bit field accessors that don't require unpacking _controlState. These depend on the bit layout and on workerCount being never negative.

Main worker run loop. Repeatedly gets tasks from queue and executes them, while coping with a number of issues: 1. We may start out with an initial task, in which case we don't need to get the first one. Otherwise, as long as pool is running, we get tasks from GetTask. If it returns null then the worker exits due to changed pool state or configuration parameters. Other exits result from exception throws in external code, in which case completedAbruptly holds, which usually leads ProcessWorkerExit to replace this thread. 2. Before running any task, the lock is acquired to prevent other pool interrupts while the task is executing, and ClearInterruptsForTaskRun called to ensure that unless pool is stopping, this thread does not have its interrupt set. 3. Each task run is preceded by a call to BeforeExecute, which might throw an exception, in which case we cause thread to die (breaking loop with completedAbruptly true) without processing the task. 4. Assuming BeforeExecute completes normally, we run the task, gathering any of its thrown exceptions to send to AfterExecute. We separately handle RuntimeException, Error (both of which the specs guarantee that we trap) and arbitrary Throwables. Because we cannot rethrow Throwables within Runnable.run, we wrap them within Errors on the way out (to the thread's UncaughtExceptionHandler). Any thrown exception also conservatively causes thread to die. 5. After task.run completes, we call AfterExecute, which may also throw an exception, which will also cause thread to die. According to JLS Sec 14.20, this exception is the one that will be in effect even if task.run throws. The net effect of the exception mechanics is that AfterExecute and the thread's UncaughtExceptionHandler have as accurate information as we can provide about any problems encountered by user code. the worker to run

Transitions to TERMINATED state if either (SHUTDOWN and pool and queue empty) or (STOP and pool empty). If otherwise eligible to terminate but workerCount is nonzero, interrupts an idle worker to ensure that shutdown signals propagate. This method must be called following any action that might make termination possible -- reducing worker count or removing tasks from the queue during shutdown. The method is non-private to allow access from ScheduledThreadPoolExecutor.