Use this page to support ORB service advanced settings. This support includes ORB listener keep alive, ORB SSL listener keep alive, control threads, workload profile.
To view this administrative console page, click Servers > Application Servers > server name > ORB service > Advanced Settings.
Configuration tab
This option verifies that idle sessions are still valid by polling the client TCP/IP stack. If the client goes away without notifying the server, it would unnecessarily leave the session active on the server side. Use property to clean up these unnecessary sessions. If the client does not respond, the session closes. The default is zero. If the property is not set, the TCP/IP option is not set. Setting the SOCK_TCP_KEEPALIVE option generates network traffic on idle sessions, which can be undesirable.
Data type | Integer |
Range | 0 - 2147460 |
This option verifies if idle sessions are still valid by polling the client TCP/IP stack. If the client goes away without notifying the server, it would unnecessarily leave the session active on the server side. Use this option to clean up these unnecessary sessions. If the client does not respond, the session closes. The default is zero. If the property is not set, the TCP/IP option is not set. Setting the SOCK_TCP_KEEPALIVE option generates network traffic on idle sessions, which can be undesirable.
Data type | Integer |
Range | 0 - 2147460 |
Data type | Integer |
Range | 0 - 2147040 |
Default | 300 |
Disable workload manager queue timeout | 0 |
The Workload profile controls workload-pertinent decisions made by the WebSphere for z/OS runtime, such as the number of threads used in the server region. The default value is IOBOUND, which is the appropriate value for most applications. Use one of the other values when your application requires more threads.
Workload profile | Number of Threads | Description |
ISOLATE | 1 | Specifies that the servant region is restricted to a single application thread. Use ISOLATE to ensure that concurrently dispatched applications do not execute in the same servant. Two requests processed in the same servant can cause one request to corrupt another. |
IOBOUND | MIN(30, MAX(5,(Number of CPUs*3))) | Specifies more threads in applications that perform I/O-intensive processing on the z/OS operating system. The calculation of the thread number is based on the number of CPUs. IOBOUND is used by most applications that have a balance of CPU intensive and remote operation calls. A gateway or protocol converter are two examples of applications that use the IOBOUND profile. |
CPUBOUND | MAX((Number of CPUs-1),3) | Specifies that the application performs processor-intensive operations on the z/OS operating system, and therefore would not benefit from more threads than the number of CPUs. The calculation of the thread number is based on the number of CPUs. Use the CPUBOUND profile setting in CPU intensive applications, like XML parsing and XML document construction, where the vast majority of the application response time is spent using the CPU. |
LONGWAIT | 40 | Specifies more threads than IOBOUND for application processing. LONGWAIT spends most of its time waiting for network/remote operations to complete. Use this setting when the application makes frequent calls to another application system, like CICS screen scraper applications, but does not do much of its own processing. |
Note: Number of CPUs is the number of CPUs online when the control region comes up.
You can check the number of worker threads using message BBOO0234I in the servant job log. See WebSphere Application Server for z/OS Messages and codes for more information.