In nearly every server application, the question of thread pools and work queues comes up.
几乎在每个服务器应用程序中都会出现线程池和工作队列问题。
Thus, the thread count continues to increase, but no additional users gain access to the server.
因此，线程数量持续增加，但是没有更多用户获得对服务器的访问权。
Thread pools are far from the only way to use multiple threads within a server application.
线程池远不是服务器应用程序内使用多线程的唯一方法。
It can be called iteratively in a server thread.
在服务器线程中可以迭代地调用它。
There is a single message listener service and a single corresponding thread pool in each server for all the listener ports defined in that server and used by all the applications.
在每个服务器中，对于该服务器中定义并由所有应用程序使用的所有侦听器端口，仅存在一个消息侦听器服务和一个相应的线程池。
If interaction was possible after the initial data was served, and the connection was kept open, then the thread could not be released and the server would not be able to serve many users.
如果提供初始数据之后仍可能存在交互，那么将连接保持为打开状态，因此线程就不能释放出来，服务器也就不能为很多用户服务。
The article also discusses how to initially configure the memory, thread pool, and JDBC connection pool on the application server.
本文还讨论了如何在应用服务器上配置内存、线程池和JDBC连接池的初始值。
The thread is responsible for all data exchange between client browser and back-end application server.
该线程负责客户端浏览器与后端应用程序服务器之间的所有数据交换。
Each application server would then perform its own dispatching within itself, using its own dispatcher thread.
然后，每个应用程序服务器都将使用自己的调度程序线程在其内执行自己的分派。
This caused each NRPC user to spawn off a server thread.
这就导致每个NRPC用户都会派生一个服务器线程。
The thread pool is a useful tool for organizing server applications.
线程池是组织服务器应用程序的有用工具。
Because application servers use limited thread pools, continuous use of a thread prevents an application server from handling other requests while sending or receiving a message using these protocols.
由于应用服务器使用有限的线程池，持续使用一个线程将使应用服务器在使用这些协议发送和接收消息时无法处理其他请求。
There is a memory overhead to hold the spot, and in the case of an application server, memory for the thread that's handling the request.
保留排队位置会导致内存开销，对于应用服务器，这会与正在处理请求的线程争用内存。
A user thread is a database server thread that services requests from client applications.
用户线程是服务来自客户机应用程序的请求的数据库服务器线程。
Configuring these thread pools is primarily a part of tuning an application server for optimal performance.
配置这些线程池主要是调优应用程序服务器以实现最优性能的调优工作的一部分。
A global thread (per server process) is responsible for creating and managing each user connection thread.
一个全局线程(每个服务器进程一个)负责创建和管理用户连接线程。
An indication of which thread in the server was responsible for emitting this message.
指示服务器中的哪个线程负责发出此消息。
It was quickly discovered that a thread is an important resource and that the application-server performance degrades significantly if the number of threads surpasses some boundary.
人们很快发现线程是种重要的资源，并且当线程数量超过某一界限后，应用服务器的性能将显著下降。
Increasing the number of threads in the thread pool has limited benefit because application-server performance starts to degrade as the number of threads in the pool increases.
增加线程池中的线程数量收效甚微，因为当线程池中的线程数量增加时，应用程序-服务器性能将开始降低。
Rather, they create a new process or thread every time a client connects to the application server.
但是有些应用程序并没有使用进程/线程池机制，而是每当客户机连接到应用程序服务器都创建新的进程。
You can then make calculations to determine the service rates for each thread (and subsequently the service rate for the entire server).
然后可以进行计算，以确定每个线程的服务速率(并据此得到整个服务器的服务速率)。
With WebSphere Application Server v4.0 and later, the thread pool defines minimum and maximum sizes which reflect the limits of the pool size.
在WebSphereApplicationServerV4.0和更新的版本中，线程池定义了反映池大小的限制的最小值和最大值。
Across all platforms, WebSphere Application Server implements a thread pool to process requests from clients.
在所有平台上，WebSphereApplicationServer均实现线程池来处理客户端发出的请求。
Using the feature, the back-end call runs in a new thread, managed by Application Server, and the application does not wait for the result.
通过使用该功能，后端调用运行在ApplicationServer托管的新线程，并且应用程序不会等待结果。
In the first release of our plugin, the server was started as a new thread inside the Eclipse workbench.
在我们的插件的第一个版本中，服务器作为Eclipse工作台内部的一个新的线程启动。
Because the server runs on a separate thread, main exits once it is up and running.
由于服务器是在单独的线程上运行的，因此只要启动并运行，main就退出。
The portlet displays the thread pools available on the server and the size of each pool (Figure 1).
此Portlet显示了服务器上的可用线程池以及每个池的大小(图1)。
The application server then associates this transaction with the thread of execution before calling the work object's run method.
然后应用服务器会在调用工作对象的run方法之前把这个事务与执行线程关联起来。
This is a scalable way of servicing Web requests asynchronously without tying up all of the connection and thread resources on a server.
这是一种异步服务Web请求的可扩展方式，无需在服务器上输入所有连接和线程资源。
The solution provided shows how to separate the long running call into another managed thread by using the Websphere Application Server feature of Asynchronous Beans.
这种解决方案展示了如何利用WebsphereApplicationServer的异步bean功能将耗时的调用分离到另一个托管线程中。
应用推荐