It dynamically correlates events occurring on a single application thread.
它动态地把发生在同一应用线程上的事件联系起来。
The kernel thread and the application thread will handshake with each other.
内核线程和应用程序线程需要相互进行握手。
The application thread is only initialized for com interop if the thread actually makes a call to a com component.
如果应用程序线程实际调用了COM组件，则仅为COM互操作初始化该线程。
Each thread in the application will have its own local variable time, thus enabling each application thread to track its time.
应用程序中的每个线程都有自己的局部变量time，因此每个应用程序线程可以跟踪自己的时间。
Do not use the main application thread to make a remote call, as this would cause the application to become unresponsive while you wait on the remote server.
不要使用主应用程序线程发出远程调用，因为这将使应用程序在等待远程服务器响应时失去响应性。
When called by the application, the plug-in serializer runs in the same thread as the application and can only access elements created within the application thread.
应用程序调用插件序列化程序时，插件序列化程序与应用程序在同一线程中运行，且仅能访问应用程序线程中创建的元素。
Unfortunately, the finalizer thread was running at a lower priority than another application thread, so objects weren't getting finalized at the rate they became eligible for finalization.
遗憾的是，终结方法线程的运行优先级要低于另一个应用线程，因此在另一个应用线程中的对象变得可以被终结时，它们不能被终结。
In nearly every server application, the question of thread pools and work queues comes up.
几乎在每个服务器应用程序中都会出现线程池和工作队列问题。
This does not require any changes to the application code and provides timestamp, thread id, and parameter information.
这不需要对应用程序代码做任何修改，它会提供时间戳、线程ID和参数信息。
Of course, you should have an additional thread in the application to capture transaction correlation data so that neither the core transaction performance nor response time is affected.
当然，这些应用程序中还应该有额外的线程来获取事务关联数据以免核心事务性能和响应时间受到影响。
Recommendation: Test the application with a variety of minimum and maximum thread pool sizes to determine which Settings move as much work as possible through the application.
推荐：请用不同的最小和最大线程池大小来测试应用程序以确定哪些设置使应用程序完成尽可能多的工作。
The article also discusses how to initially configure the memory, thread pool, and JDBC connection pool on the application server.
本文还讨论了如何在应用服务器上配置内存、线程池和JDBC连接池的初始值。
This is achieved by applying and removing the J2EE context information on and off the thread when the application logic begins and ends.
当应用程序逻辑开始和终止时，这可以通过应用和删除线程内外的J2EE上下文信息来完成。
Although the amount of memory used per thread is quite small, for an application with several hundred threads, the total memory use for thread stacks can be large.
虽然每个线程使用的内存量相当少，但对于拥有几百个线程的应用程序，线程栈的内存使用总量会达到很高。
Of course, it can't release them until the thread pool itself is released by the application.
当然，直到它本身被应用程序释放之后，线程池才能释放线程。
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.
由于应用服务器使用有限的线程池，持续使用一个线程将使应用服务器在使用这些协议发送和接收消息时无法处理其他请求。
You can avoid this problem by performing application initialization from a high-priority RT thread.
您可以通过从一个高优先级rt线程执行应用程序初始化来避免这个问题。
This approach doesn't waste resources, since the application isn't holding on to a thread or a process when it doesn't need them.
这种方法不会浪费资源，因为应用在不需要线程或进程的时候并不会占用它们。
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.
保留排队位置会导致内存开销，对于应用服务器，这会与正在处理请求的线程争用内存。
The point here is that if your code is running on the UI thread, the application can't handle UI events from the OS.
问题的重点在于如果UI线程在运行您的代码，应用程序将无法再处理来自OS的UI事件。
Configuring these thread pools is primarily a part of tuning an application server for optimal performance.
配置这些线程池主要是调优应用程序服务器以实现最优性能的调优工作的一部分。
To run COBOL programs in more than one thread, you must compile all of the COBOL programs in the application with the thread compiler option.
要在多个线程中运行COBOL程序，必须在应用程序中使用THREAD编译器选项对所有COBOL程序进行编译。
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均实现线程池来处理客户端发出的请求。
It is also the thread where your application interacts with running components of the Android UI toolkit.
同时，它还是你的应用程序与AndroidUI toolkit中运行的组件进行交互的线程。
Many application today block a thread in the server to wait for an external web service call.
如今许多应用程序都在服务器端阻塞线程，以等待一个外部的Web服务调用。
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 most cases, for each connection by a client application, Informix runs one sqlexec thread.
在多数情况下，对于一个客户机应用程序的每个连接，Informix运行一个sqlexec线程。
Pool allocation does not work effectively if one thread of the application allocates memory and other thread frees the memory.
如果应用程序的一个线程分配内存，而其他线程释放内存，那么poolallocation实际上是无效的。
Pool allocation does not work effectively if one thread of the application allocates memory and other thread frees the memory.
如果应用程序的一个线程分配内存，而其他线程释放内存，那么poolallocation实际上是无效的。
应用推荐