此池曾因积污太厚，池水日浅。
返回此池的目标并行度。
此规则不仅适用于向数据池添加值，然后使用它们，而且还适用于直接在对象之间复制和粘贴值。
This rule applies not only to adding values to the data pool and then using them, but also when you directly copy and paste values between objects.
不过，对于上述的“可增长线程池”，此解决方案并不是十全十美：在AIO工具中排队会带来额外的开销和延迟。
However, as in the case of "growable thread pools" above, this solution is not perfect: queuing in the AIO facility introduces additional overhead and latency.
如果为其中一个示例创建新的模拟配置文件，则也需要设置此资源池。
If you create a new simulation profile for one of the examples, you will need to set this up as well.
此角色用于分配rid池，以便新的或现有的域控制器能够创建用户帐户、计算机帐户或安全组。
This role is required to allocate the RID pool so that new or existing domain controllers can create user accounts, computer accounts or security groups.
缺省情况下，池维护的线程每180秒(3分钟)运行一次，但是通过设置连接池获得时间属性可以更改此值。
By default, the pool maintained thread runs every 180 seconds (3 minutes), although this value can be changed by setting the connection pool Reap time property.
增大最大连接池大小可以帮助缓解此问题。
Increasing the maximum connection pool size might help to alleviate the problem.
此脚本适度地增加线程池以保证CPU能够接受。
This script increased the thread pool in order to keep the CPU entertained.
每个bean类都可以使用此元素来定义自己的空闲池的大小。
Each bean class can define the size of its own free pool using this element.
通过使用EMPdemo示例提供的数据库池部署计划，我们将向您介绍如何理解和修改此计划以制定自己的数据库部署计划。
By using the database pool deployment plan provided by the EMPdemo sample, we will show you how to understand and modify this plan to build your own database deployment plan.
将JDBC连接池嵌入单一部署的企业应用程序中。但是，当使用此方法时，该应用程序必须作为 .ear文件进行绑定。
Embed the JDBC connection pool into a single-deployed enterprise application, though, when using this method, the application must be bundled as an .ear file.
此Portlet显示了服务器上的可用线程池以及每个池的大小(图1)。
The portlet displays the thread pools available on the server and the size of each pool (Figure 1).
最后，CustomerService实用程序向您展示了如何在代码内访问此连接池。
Finally, the Customer Service utility showed you how this connection pool can be accessed within the code.
有关使用此工具分析连接池问题所需要的WebSphereApplicationServer跟踪设置，请参阅 MustGather信息。
See MustGather information for the WebSphere Application Server trace settings required for this tool to analyse connection pool issues.
在大多数情况下，无需调整此线程池，因为Web容器线程是无阻塞的，并且可以同时处理多个MDM服务请求。
In most cases, this thread pool does not need to be adjusted because Web container threads are non-blocking and can handle multiple MDM service requests concurrently.
此区域可以查看等待连接WebSphere连接池连接所花费的等待时间。
This area provides insight into the time spent waiting for a connection for the WebSphere connection pool.
name元素定义其他模块将用于引用此连接池的名称。
The name element defines the name that other modules will use to refer to this connection pool.
这此，缓冲池快照的重要元素将重点放在了下面。
This time the important elements of the buffer pool snapshot that should be focused on are below.
必须配置此messagelistener线程池，以使足够的并发达到性能要求。
This pool, the MessageListener Thread pool, must be configured to enable sufficient concurrency to achieve the performance requirement.
此线程池管理与WebSphereApplicationServer的分布式版本稍有不同。
This thread pool management is a bit different from distributed versions of WebSphere Application Server.
返回可识别此线程池的字符串及它的状态，包括运行状态、并行级别、工作线程和任务数量。
Returns a string identifying this pool, as well as its state, including indications of run state, parallelism level, and worker and task counts.
当系统中存在多个线程池时，此方法或许对于此类的扩展类在进行作业重新分配时是有用的。
This method may be useful in extensions to this class that re-assign work in systems with multiple pools.
此方法在有线程池线程变得可用时执行。
The method executes when a thread pool thread becomes available.
此方法在有线程池线程变得可用时执行。
The method executes when a thread pool thread becomes available.
应用推荐