731f52fdf7
Motiviation: Sometimes it is useful to allow to specify a custom strategy to handle rejected tasks. For example if someone tries to add tasks from outside the eventloop it may make sense to try to backoff and retries and so give the executor time to recover. Modification: Add RejectedEventExecutor interface and implementations and allow to inject it. Result: More flexible handling of executor overload.
29 lines
1.0 KiB
Java
29 lines
1.0 KiB
Java
/*
|
|
* Copyright 2016 The Netty Project
|
|
*
|
|
* The Netty Project licenses this file to you under the Apache License,
|
|
* version 2.0 (the "License"); you may not use this file except in compliance
|
|
* with the License. You may obtain a copy of the License at:
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
* WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
* License for the specific language governing permissions and limitations
|
|
* under the License.
|
|
*/
|
|
package io.netty.util.concurrent;
|
|
|
|
/**
|
|
* Similar to {@link java.util.concurrent.RejectedExecutionHandler} but specific to {@link SingleThreadEventExecutor}.
|
|
*/
|
|
public interface RejectedExecutionHandler {
|
|
|
|
/**
|
|
* Called when someone tried to add a task to {@link SingleThreadEventExecutor} but this failed due capacity
|
|
* restrictions.
|
|
*/
|
|
void rejected(Runnable task, SingleThreadEventExecutor executor);
|
|
}
|