Thread System
Purpose
The AS Java thread system is responsible for handling system and client threads. It comprises two managers – Thread Manager and Application Thread Manager. All threads in which AS Java system operations are executed (core, services, and so on) use system threads supplied by the Thread Manager. Application Thread Manager supplies the threads in which the code of the client application is executed. When an HTTP request reaches the AS Java, an application thread receives it.
Features
The separation of the thread system into application and system thread pools enables the AS Java to sustain greater system load without disrupting its normal work.
● Application Thread Manager
It handles client requests coming to the system. 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.
● Thread Manager
The Thread Manager pool is used for system activities such as internal cluster communication, event processing, backup of log records, background processes for collecting and storing data, and so on. The logic in the system Thread Manager is similar to the application logic – the system uses a queue for system requests if a free thread is not available.
With these two thread pools, the AS Java saves resources for system requirements and prevents situations where there are too many clients that block the system.
You can monitor thread system information using the SAPManagement Console.
More information:
Monitoring the
Application Server with the SAP MC
More information about the AS Java thread system configuration: