线程池拒绝策略-CallerRunsPolicy

已于 2023-12-08 15:17:21 修改
阅读量356 收藏
点赞数
分类专栏： Java 文章标签： java
于 2023-12-08 15:16:44 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/OldFat_/article/details/134879210
版权

线程池拒绝策略-CallerRunsPolicy

官方说明: 被拒绝任务的处理程序，它直接在execute方法的调用线程中运行被拒绝的任务，除非执行器已关闭，在这种情况下，该任务将被丢弃。

    /**
     * A handler for rejected tasks that runs the rejected task
     * directly in the calling thread of the {@code execute} method,
     * unless the executor has been shut down, in which case the task
     * is discarded.
     */
    public static class CallerRunsPolicy implements RejectedExecutionHandler {
        /**
         * Creates a {@code CallerRunsPolicy}.
         */
        public CallerRunsPolicy() { }

        /**
         * Executes task r in the caller's thread, unless the executor
         * has been shut down, in which case the task is discarded.
         *
         * @param r the runnable task requested to be executed
         * @param e the executor attempting to execute this task
         */
        public void rejectedExecution(Runnable r, ThreadPoolExecutor e) {
            if (!e.isShutdown()) {
                r.run();
            }
        }
    }

代码实验：观察CallerRunsPolicy运行机制

public static void main(String[] args) {
        LinkedBlockingQueue<Runnable> queue = new LinkedBlockingQueue<>(10);
        ThreadPoolExecutor threadPoolExecutor = new ThreadPoolExecutor(
                3,
                5,
                5,
                TimeUnit.MINUTES,
                queue,
                NAMED_ORDER_SYNC,
                new ThreadPoolExecutor.CallerRunsPolicy());
        for (int i = 0; i < 100; i++) {
            threadPoolExecutor.execute(() -> {
                System.out.println("当前执行线程为:" +Thread.currentThread().getName() + "   activeCount: "+threadPoolExecutor.getActiveCount() + " - largestPoolSize:" + threadPoolExecutor.getLargestPoolSize() + " - queueSize:" + threadPoolExecutor.getQueue().size());
                try {
                    TimeUnit.SECONDS.sleep(2);
                } catch (InterruptedException e) {
                    e.printStackTrace();
                }
            });
        }
    }

实验结果：可以看到，当阻塞队列打满后且达到最大线程数时，新加入的任务会使用提交者，也就是主线程去执行。此时整体的执行情况是线程池和主线程共同执行任务，直到任务执行完毕。

/iCoding/java/jdk8u242-b08/bin/java -javaagent:/iCoding/ideaIU-2021.3.2/ide/lib/idea_rt.jar=48779:/iCoding/ideaIU-2021.3.2/ide/bin -Dfile.encoding=UTF-8 -classpath /iCoding/java/jdk8u242-b08/jre/lib/charsets.jar:/iCoding/java/jdk8u242-b08/jre/lib/ext/cldrdata.jar:/iCoding/java/jdk8u242-b08/jre/lib/ext/dnsns.jar:/iCoding/java/jdk8u242-b08/jre/lib/ext/jaccess.jar:/iCoding/java/jdk8u242-b08/jre/lib/ext/localedata.jar:/iCoding/java/jdk8u242-b08/jre/lib/ext/nashorn.jar:/iCoding/java/jdk8u242-b08/jre/lib/ext/sunec.jar:/iCoding/java/jdk8u242-b08/jre/lib/ext/sunjce_provider.jar:/iCoding/java/jdk8u242-b08/jre/lib/ext/sunpkcs11.jar:/iCoding/java/jdk8u242-b08/jre/lib/ext/zipfs.jar:/iCoding/java/jdk8u242-b08/jre/lib/jce.jar:/iCoding/java/jdk8u242-b08/jre/lib/jsse.jar:/iCoding/java/jdk8u242-b08/jre/lib/management-agent.jar:/iCoding/java/jdk8u242-b08/jre/lib/resources.jar:/iCoding/java/jdk8u242-b08/jre/lib/rt.jar:/root/codes/baidu_health_tradeflow-b2c/baidu/health/tc-search/tc-search-common/target/classes:/root/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar:/root/.m2/repository/ch/qos/logback/logback-core/1.2.3/logback-core-1.2.3.jar:/root/.m2/repository/org/slf4j/slf4j-api/1.7.31/slf4j-api-1.7.31.jar:/root/.m2/repository/org/springframework/spring-core/5.0.11.RELEASE/spring-core-5.0.11.RELEASE.jar:/root/.m2/repository/org/springframework/spring-jcl/5.0.11.RELEASE/spring-jcl-5.0.11.RELEASE.jar:/root/.m2/repository/org/springframework/spring-context/5.0.11.RELEASE/spring-context-5.0.11.RELEASE.jar:/root/.m2/repository/org/springframework/spring-aop/5.0.11.RELEASE/spring-aop-5.0.11.RELEASE.jar:/root/.m2/repository/org/springframework/spring-beans/5.0.11.RELEASE/spring-beans-5.0.11.RELEASE.jar:/root/.m2/repository/org/springframework/spring-expression/5.0.11.RELEASE/spring-expression-5.0.11.RELEASE.jar:/root/.m2/repository/org/springframework/boot/spring-boot/2.0.7.RELEASE/spring-boot-2.0.7.RELEASE.jar:/root/.m2/repository/org/apache/commons/commons-lang3/3.7/commons-lang3-3.7.jar:/root/.m2/repository/org/springframework/boot/spring-boot-autoconfigure/2.0.7.RELEASE/spring-boot-autoconfigure-2.0.7.RELEASE.jar:/root/.m2/repository/com/github/rholder/guava-retrying/2.0.0/guava-retrying-2.0.0.jar:/root/.m2/repository/com/google/guava/guava/19.0/guava-19.0.jar:/root/.m2/repository/com/google/code/findbugs/jsr305/2.0.2/jsr305-2.0.2.jar:/root/.m2/repository/commons-codec/commons-codec/1.11/commons-codec-1.11.jar:/root/.m2/repository/cn/hutool/hutool-all/5.5.9/hutool-all-5.5.9.jar:/root/.m2/repository/com/baidu/health/doraemon-api/1.0.8-SNAPSHOT/doraemon-api-1.0.8-20211227.150145-12.jar:/root/.m2/repository/org/mapstruct/mapstruct-jdk8/1.2.0.Final/mapstruct-jdk8-1.2.0.Final.jar:/root/.m2/repository/org/projectlombok/lombok/1.16.22/lombok-1.16.22.jar:/root/.m2/repository/org/mapstruct/mapstruct-processor/1.2.0.Final/mapstruct-processor-1.2.0.Final.jar:/root/.m2/repository/com/alibaba/transmittable-thread-local/2.12.4/transmittable-thread-local-2.12.4.jar:/root/.m2/repository/com/baidu/health/doraemon-logger/1.1.8/doraemon-logger-1.1.8.jar:/root/.m2/repository/com/fasterxml/jackson/core/jackson-annotations/2.11.2/jackson-annotations-2.11.2.jar:/root/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.11.2/jackson-core-2.11.2.jar:/root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.11.2/jackson-databind-2.11.2.jar:/root/.m2/repository/com/fasterxml/jackson/datatype/jackson-datatype-jsr310/2.11.2/jackson-datatype-jsr310-2.11.2.jar:/root/.m2/repository/com/baidu/health/doraemon-agent-starter/1.0.3-SNAPSHOT/doraemon-agent-starter-1.0.3-20230714.103958-8.jar:/root/.m2/repository/com/baidu/health/doraemon-kernel/1.0.3-SNAPSHOT/doraemon-kernel-1.0.3-20230714.103911-8.jar:/root/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib/1.6.20/kotlin-stdlib-1.6.20.jar:/root/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib-common/1.6.20/kotlin-stdlib-common-1.6.20.jar:/root/.m2/repository/org/jetbrains/annotations/13.0/annotations-13.0.jar:/root/.m2/repository/com/squareup/okhttp3/okhttp/4.10.0/okhttp-4.10.0.jar:/root/.m2/repository/com/squareup/okio/okio-jvm/3.0.0/okio-jvm-3.0.0.jar:/root/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.2.71/kotlin-stdlib-jdk8-1.2.71.jar:/root/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib-jdk7/1.2.71/kotlin-stdlib-jdk7-1.2.71.jar:/root/.m2/repository/net/bytebuddy/byte-buddy/1.13.0/byte-buddy-1.13.0.jar:/root/.m2/repository/net/bytebuddy/byte-buddy-agent/1.13.0/byte-buddy-agent-1.13.0.jar:/root/.m2/repository/com/google/auto/service/auto-service-annotations/1.0.1/auto-service-annotations-1.0.1.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-api/1.21.0/opentelemetry-api-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-context/1.21.0/opentelemetry-context-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-sdk/1.21.0/opentelemetry-sdk-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-sdk-common/1.21.0/opentelemetry-sdk-common-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-sdk-trace/1.21.0/opentelemetry-sdk-trace-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-sdk-metrics/1.21.0/opentelemetry-sdk-metrics-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-sdk-logs/1.21.0-alpha/opentelemetry-sdk-logs-1.21.0-alpha.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-api-logs/1.21.0-alpha/opentelemetry-api-logs-1.21.0-alpha.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-exporter-common/1.21.0/opentelemetry-exporter-common-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-exporter-jaeger/1.21.0/opentelemetry-exporter-jaeger-1.21.0.jar:/root/.m2/repository/com/fasterxml/jackson/jr/jackson-jr-objects/2.11.2/jackson-jr-objects-2.11.2.jar:/root/.m2/repository/io/opentelemetry/javaagent/opentelemetry-javaagent-extension-api/1.23.0-alpha/opentelemetry-javaagent-extension-api-1.23.0-alpha.jar:/root/.m2/repository/net/bytebuddy/byte-buddy-dep/1.13.0/byte-buddy-dep-1.13.0.jar:/root/.m2/repository/org/ow2/asm/asm/9.4/asm-9.4.jar:/root/.m2/repository/org/ow2/asm/asm-commons/9.4/asm-commons-9.4.jar:/root/.m2/repository/io/opentelemetry/instrumentation/opentelemetry-instrumentation-api/1.23.0/opentelemetry-instrumentation-api-1.23.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-sdk-extension-autoconfigure/1.23.1-alpha/opentelemetry-sdk-extension-autoconfigure-1.23.1-alpha.jar:/root/.m2/repository/io/jaegertracing/jaeger-client/1.8.1/jaeger-client-1.8.1.jar:/root/.m2/repository/io/jaegertracing/jaeger-thrift/1.8.1/jaeger-thrift-1.8.1.jar:/root/.m2/repository/org/apache/thrift/libthrift/0.15.0/libthrift-0.15.0.jar:/root/.m2/repository/io/jaegertracing/jaeger-core/1.8.1/jaeger-core-1.8.1.jar:/root/.m2/repository/io/opentracing/opentracing-api/0.33.0/opentracing-api-0.33.0.jar:/root/.m2/repository/io/opentracing/opentracing-util/0.33.0/opentracing-util-0.33.0.jar:/root/.m2/repository/io/opentracing/opentracing-noop/0.33.0/opentracing-noop-0.33.0.jar:/root/.m2/repository/io/jaegertracing/jaeger-tracerresolver/1.8.1/jaeger-tracerresolver-1.8.1.jar:/root/.m2/repository/io/opentracing/contrib/opentracing-tracerresolver/0.1.8/opentracing-tracerresolver-0.1.8.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-exporter-jaeger-thrift/1.21.0/opentelemetry-exporter-jaeger-thrift-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-exporter-logging/1.21.0/opentelemetry-exporter-logging-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-semconv/1.21.0-alpha/opentelemetry-semconv-1.21.0-alpha.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-sdk-extension-autoconfigure-spi/1.21.0/opentelemetry-sdk-extension-autoconfigure-spi-1.21.0.jar:/root/.m2/repository/io/opentelemetry/opentelemetry-sdk-extension-jaeger-remote-sampler/1.21.0/opentelemetry-sdk-extension-jaeger-remote-sampler-1.21.0.jar:/root/.m2/repository/com/baidu/health/doraemon-bdrp-javaagent/1.0.3-SNAPSHOT/doraemon-bdrp-javaagent-1.0.3-20230714.103924-8.jar:/root/.m2/repository/com/baidu/health/doraemon-bdrp-common/1.0.3-SNAPSHOT/doraemon-bdrp-common-1.0.3-20230714.103916-8.jar:/root/.m2/repository/com/baidu/health/doraemon-starlight-javaagent/1.0.3-SNAPSHOT/doraemon-starlight-javaagent-1.0.3-20230714.103947-8.jar:/root/.m2/repository/com/baidu/health/doraemon-starlight-library/1.0.3-SNAPSHOT/doraemon-starlight-library-1.0.3-20230714.103950-8.jar:/root/.m2/repository/com/baidu/health/doraemon-mybatis-library/1.0.3-SNAPSHOT/doraemon-mybatis-library-1.0.3-20230714.103955-8.jar:/root/codes/baidu_health_tradeflow-b2c/baidu/health/tc-search/tc-search-api/target/classes:/root/.m2/repository/com/baidu/cloud/spring-cloud-baidu-thirdparty-commons/2020.0.2-SNAPSHOT/spring-cloud-baidu-thirdparty-commons-2020.0.2-20210127.131051-2.jar:/root/.m2/repository/com/baidu/health/tradecenter-api/1.1.1-SNAPSHOT/tradecenter-api-1.1.1-20220701.065616-12.jar:/root/.m2/repository/javax/validation/validation-api/2.0.1.Final/validation-api-2.0.1.Final.jar:/root/.m2/repository/com/baidu/cloud/spring-cloud-starter-baidu-redis/2022.0.4/spring-cloud-starter-baidu-redis-2022.0.4.jar:/root/.m2/repository/org/springframework/boot/spring-boot-starter/2.0.7.RELEASE/spring-boot-starter-2.0.7.RELEASE.jar:/root/.m2/repository/org/springframework/boot/spring-boot-starter-logging/2.0.7.RELEASE/spring-boot-starter-logging-2.0.7.RELEASE.jar:/root/.m2/repository/org/apache/logging/log4j/log4j-to-slf4j/2.10.0/log4j-to-slf4j-2.10.0.jar:/root/.m2/repository/org/apache/logging/log4j/log4j-api/2.10.0/log4j-api-2.10.0.jar:/root/.m2/repository/org/slf4j/jul-to-slf4j/1.7.31/jul-to-slf4j-1.7.31.jar:/root/.m2/repository/javax/annotation/javax.annotation-api/1.3.2/javax.annotation-api-1.3.2.jar:/root/.m2/repository/org/yaml/snakeyaml/1.19/snakeyaml-1.19.jar:/root/.m2/repository/org/springframework/boot/spring-boot-starter-data-redis/2.0.7.RELEASE/spring-boot-starter-data-redis-2.0.7.RELEASE.jar:/root/.m2/repository/org/springframework/data/spring-data-redis/2.0.12.RELEASE/spring-data-redis-2.0.12.RELEASE.jar:/root/.m2/repository/org/springframework/data/spring-data-keyvalue/2.0.12.RELEASE/spring-data-keyvalue-2.0.12.RELEASE.jar:/root/.m2/repository/org/springframework/data/spring-data-commons/2.0.12.RELEASE/spring-data-commons-2.0.12.RELEASE.jar:/root/.m2/repository/org/springframework/spring-tx/5.0.11.RELEASE/spring-tx-5.0.11.RELEASE.jar:/root/.m2/repository/org/springframework/spring-oxm/5.0.11.RELEASE/spring-oxm-5.0.11.RELEASE.jar:/root/.m2/repository/org/springframework/spring-context-support/5.0.11.RELEASE/spring-context-support-5.0.11.RELEASE.jar:/root/.m2/repository/io/lettuce/lettuce-core/5.0.5.RELEASE/lettuce-core-5.0.5.RELEASE.jar:/root/.m2/repository/io/projectreactor/reactor-core/3.1.12.RELEASE/reactor-core-3.1.12.RELEASE.jar:/root/.m2/repository/org/reactivestreams/reactive-streams/1.0.2/reactive-streams-1.0.2.jar:/root/.m2/repository/io/netty/netty-common/4.1.31.Final/netty-common-4.1.31.Final.jar:/root/.m2/repository/io/netty/netty-transport/4.1.31.Final/netty-transport-4.1.31.Final.jar:/root/.m2/repository/io/netty/netty-buffer/4.1.31.Final/netty-buffer-4.1.31.Final.jar:/root/.m2/repository/io/netty/netty-resolver/4.1.31.Final/netty-resolver-4.1.31.Final.jar:/root/.m2/repository/io/netty/netty-handler/4.1.31.Final/netty-handler-4.1.31.Final.jar:/root/.m2/repository/io/netty/netty-codec/4.1.31.Final/netty-codec-4.1.31.Final.jar:/root/.m2/repository/org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0.jar:/root/.m2/repository/com/baidu/bdrp-client/1.1.35-SNAPSHOT/bdrp-client-1.1.35-20221117.104652-11.jar:/root/.m2/repository/redis/clients/jedis/2.9.0/jedis-2.9.0.jar:/root/.m2/repository/com/baidu/bns-client-spring/1.4.12-SNAPSHOT/bns-client-spring-1.4.12-20221117.103626-3.jar:/root/.m2/repository/com/baidu/bns-core/1.4.12-SNAPSHOT/bns-core-1.4.12-20221117.103620-3.jar:/root/.m2/repository/com/google/code/gson/gson/2.8.5/gson-2.8.5.jar:/root/.m2/repository/com/google/protobuf/protobuf-java/3.19.4/protobuf-java-3.19.4.jar:/root/.m2/repository/com/baidu/searchbox/blog4j-sdk/1.4.2-SNAPSHOT/blog4j-sdk-1.4.2-20191009.032601-43.jar:/root/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar:/root/.m2/repository/junit/junit/4.12/junit-4.12.jar:/root/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar:/root/.m2/repository/org/apache/commons/commons-collections4/4.1/commons-collections4-4.1.jar com.baidu.health.tcsearch.common.util.ThreadPoolUtil
当前执行线程为:sync-or-search   activeCount: 3 - largestPoolSize:3 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:4 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 3 - largestPoolSize:4 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:5
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:5
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:5
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:4
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:4
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:3
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:5
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:4
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:5
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:5
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:3
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:5
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:5
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:8
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:9
当前执行线程为:main   activeCount: 5 - largestPoolSize:5 - queueSize:10
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:6
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:7
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:4
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:5
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:4
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:5 - queueSize:3
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:5 - queueSize:1
当前执行线程为:sync-or-search   activeCount: 5 - largestPoolSize:5 - queueSize:0
当前执行线程为:sync-or-search   activeCount: 4 - largestPoolSize:5 - queueSize:1

Process finished with exit code 137 (interrupted by signal 9: SIGKILL)
OldFat_
关注
专栏目录
线程池-线程池的拒绝策略
欢迎订阅我的“JAVA全栈开发笔记（全）”专栏，价格优惠，仅需19.9元。
05-18 635
AbortPolicy（中止策略） CallerRunsPolicy（调用者运行策略） DiscardPolicy（丢弃策略） DiscardOldestPolicy（弃老策略）
自定义线程池拒绝策略
BUG指挥课堂
07-05 5059
一. 默认的拒绝策略 ThreadPoolExceutor.AbortPolicy : 丢弃任务并抛出RejectedExecutionException异常。 ThreadPoolExecutor.DiscardPolicy：丢弃任务，但是不抛出异常。 ThreadPoolExecutor.DiscardOldestPolicy：丢弃队列最前面的任务，然后重新提交被拒绝的任务 ThreadPoolExecutor.CallerRunsPolic
CallerRunsPolicy会阻塞主线程吗
咖啡攻城狮的博客
01-09 6069
ThreadPoolExecutor实现原理分析
线程池拒绝策略——CallerRunsPolicy
热门推荐
qq_22253853的博客
06-30 3万+
最近在搞线程池，用到了CallerRunsPolicy这个拒绝策略。 为什么选用CallerRunsPolicy？ 因为考虑到数据一条都不能丢失，所以选择了CallerRunsPolicy策略。保证数据来了不会丢。天真的幻想着这策略好啊！ 经过了一段时间的实战考验，发现了一个问题，数据处理不过来，经常堆积，这样还行能接受。 遇到什么问题？ 在从单线程改用多线程后，阻塞队列在高峰期时经常是满的。 阻塞队列经常是满了，于是考虑从处理效率上入手，（同事解决的）优化了程序处理速度和数据库写入效率，缓解了这个问题，线
Java线程池原理解析-ThreadPoolExecutor
最新发布
admin3211的博客
07-23 538
【代码】Java线程池原理解析-ThreadPoolExecutor。
线程池的拒绝策略CallerRunsPolicy
weixin_41262132的博客
02-11 1097
用于运行被拒绝任务的被拒绝任务的处理程序 直接在{@code execute}方法的调用创建线程池的线程中， 除非线程池已经关闭，在这种情况下，任务 就会被丢弃。
大多数人不知道的：线程池CallerRunsPolicy()拒绝策略
Java知音
09-23 3381
点击关注公众号，实用技术文章及时了解来源：blog.csdn.net/dabusiGin/article/details/105323796在学习CallerRunsPolicy拒绝策略的...
RejectedPolicy--CallerRunsPolicy
Cages的专栏
02-28 208
  package com.jerry.concurrency; import java.util.concurrent.ArrayBlockingQueue; import java.util.concurrent.ThreadPoolExecutor; import java.util.concurrent.TimeUnit; public class TestCallerRun...
ThreadPoolExecutor里面4种拒绝策略--CallerRunsPolicy
chikoucha6215的博客
08-19 7484
首先介绍一下ThreadPoolExecutor构造方法： public ThreadPoolExecutor(int corePoolSize, int maximumPoolSize, ...
线程池的拒绝策略
taokeng的博客
04-02 154
今天在工作的时候，遇见了一个线程阻塞的问题，然后定位代码，找出了问题的所在： ​ 这是我们线程池的初始化代码： RejectedExecutionHandler handler = new ThreadPoolExecutor.DiscardPolicy(); executor = new ThreadPoolExecutor(5, 20, 60, TimeUnit.SECONDS, new ...
java 自定义拒绝策略,线程池拒绝策略-RejectedExecutionHandler
weixin_33708562的博客
03-14 1124
当线程池中的线程数目达到maximumPoolSize，且任务缓存队列已满时，如果还有任务到来就会采取任务拒绝策略，通常有以下四种策略：ThreadPoolExecutor.AbortPolicy:丢弃任务并抛出RejectedExecutionException异常。ThreadPoolExecutor.DiscardPolicy：也是丢弃任务，但是不抛出异常。ThreadPoolExecuto...
线程池拒绝策略 CallerRunsPolicy
07-25
- *1* *2* [线程池拒绝策略——CallerRunsPolicy](https://blog.csdn.net/qq_22253853/article/details/107050972)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_...
线程池CallerRunsPolicy()拒绝策略
xuna118的博客
02-07 381
CallerRunsPolicy拒绝策略
一种关于ThreadPoolExecutor拒绝策略之CallerRunsPolicy（调用者运行策略）的实验研究
m0_58639137的博客
11-09 2083
线程池 CallerRunsPolicy 拒绝策略
【线程池】线程池原理与参数调优、拒绝策略-CallerRunsPolicy
后端研发工程师Marion的博客
08-23 1327
3. DiscardOldestPolicy：丢弃等待队列中最旧的任务，并执⾏当前任务。2. CallerRunsPolicy：只⽤调⽤者所在的线程来处理任务。1. AbortPolicy：直接丢弃任务，抛出异常，这是默认策略。4. DiscardPolicy：直接丢弃任务，也不抛出异常。
线程池拒绝策略
人生就像一场戏
12-02 5301
在学习CallerRunsPolicy拒绝策略的时候，搜索了很多相关的知识，其他博主的描述是这样的： 在学习CallerRunsPolicy拒绝策略的时候，搜索了很多相关的知识，其他博主的描述是这样的： 第1种：第2种：第3种： 举个例子如下图所示，主线程就是平时执行main方法中代码的线程。 再通过一个例子详细说明： public class HanderPolicy { public static void main(String[] args) { ...
Java ThreadPoolExecutor的拒绝策略CallerRunsPolicy的一个潜在的大坑
明明如月的技术博客
05-07 2万+
一、背景 前面一篇文章转载了ThreadPoolExecutor的几种拒绝策略：https://blog.csdn.net/w605283073/article/details/89930154，讲得很不错。 但是网上介绍使用拒绝策略遇到的大坑的文章不多。 本文介绍其中一个真是故障的场景。 二、问题描述 ThreadPoolExecutor的拒绝策略常用的是DiscardPolicy...
Java 线程池的拒绝策略
CodeFlight
04-18 2427
Java 线程池的拒绝策略一共有四种，分别为`AbortPolicy`，`CallerRunsPolicy`，`DiscardPolicy`，`DiscardOldestPolicy`。下面就来说明这四种策略的不同之处。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值