ule子池已耗尽动作 [英] Mule poolExhaustedAction

问题描述

我试图确保我了解线程概要文件的poolExhaustedAction值的含义.我没有看到很多例子.

I'm trying to make sure I understand the meaning of the poolExhaustedAction values for a threading profile. I'm not seeing a lot of examples out there.

假设我在HTTP端点上有一个线程池，该线程池的maxThreadsActive设置为"16".我在短时间内收到20个入站请求(比我处理任何一个请求都要快).

Assume I have a thread pool on an HTTP endpoint that has maxThreadsActive set to "16". I receive 20 inbound requests in a short period (faster than I can process any of them).

如果poolExhaustedAction设置为"WAIT"，则最后4个请求将等待threadWaitTimeout.这是正确的吗?

If poolExhaustedAction is set to "WAIT" then the last 4 requests will wait for threadWaitTimeout. Is this correct?

如果poolExhaustedAction设置为"RUN"，则最后4个请求将使用承载请求的线程到端点来运行流程.我对此有些困惑.具体来说，如果设置为"RUN"，该服务是否会拒绝请求(假设Mule具有向其传递消息的线程)?

If poolExhaustedAction is set to "RUN" then the last 4 requests will ????...use the thread that carried the request to the endpoint to run the flow???? I'm a bit confused on this one. Specifically, if set to "RUN", will the service ever reject a request (assuming Mule has threads to deliver messages to it)?

推荐答案

您是否已阅读 http://www.mulesoft.org/documentation/display/current/Tuning+Performance ?尤其是这部分?

Have you read http://www.mulesoft.org/documentation/display/current/Tuning+Performance? Especially this part?

您的问题的答案是:

1. 是的.
2. 实际上，接收到请求的线程将用于在流中对其进行处理.当入站套接字连接超时时，该服务将开始拒绝请求，因为负责在Mule中路由请求的线程太忙而无法接受它们.

这篇关于ule子池已耗尽动作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！