eG Help

The J2EE Engine thread system is responsible for handling system and client threads. It comprises of two managers – Thread Manager and Application Thread Manager. The AppThreadsTest monitors the Application Thread Manager of the SAP Web Application server, which supplies the threads in which the client applications' source code is executed. This manager provides a set of properties for starting and managing client threads in the Java Virtual Machine. When a client request comes, the system tries to find a free thread in the Application Thread Manager and to start the execution of the request. If no free thread is available, the thread system buffers the request in a request queue. By buffering the threads and using them again, the system achieves better performance than using normal Java thread system without buffering. The Application Thread Manager runs only on server processes.

Measurement	Description	Measurement Unit	Interpretation
Active_threads	The number of threads from the thread pool which are currently executing a runnable task	Number	This measure serves as a good indicator of the server workload.
Current_pool_size	The number of threads in the thread pool, currently	Number
Max_pool_size	The maximum number of threads that can be accomodated in the thread pool.	Number
Threadpool_usage	The percentage of threads in the thread pool that are being currently utilized	Percent	If the value of this measure is high, it could indicate a heavy server workload.
Waiting_tasks	The number of tasks waiting for threads, so as to begin execution	Number
Tasks_queue_size	The capacity of the request queue where the tasks waiting for execution are stored	Number
Tasks_queue_overflow	The number of tasks waiting to be placed in the request queue, in the event that the request queue is full	Number	If the value of this measure increases consistently, it could indicate a processing bottleneck.