uCosminexus Application Server, Expansion Guide
For using the EADs session failover functionality, you need to perform tuning of the entire system including the number of maximum concurrent connections, number of maximum concurrent executions, and connection pool size to be set for EADs clients and EADs servers. This section describes the points for which the number of concurrent connections, number of concurrent executions, and connection pool size can be set in a system on which the EADs session failover functionality is used.
The following figure describes the points for which the number of concurrent connections, number of concurrent executions, and connection pool size can be set in a system on which the EADs session failover functionality is used:
Figure 7-3 Points for which the number of concurrent connections, number of concurrent executions, and connection pool size can be set
Table 7-7 Number of concurrent connections, number of concurrent executions, and connection pool size contents to be set in setting points
| Setting point | Setting location | Setting target | Setting contents |
|---|---|---|---|
| (1) | Web server | Number of maximum concurrent connections | Maximum number of concurrent connections to a Web server. |
| (2) | Redirector | Connection pool size | Pool size of the connection that is used to communicate with a J2EE server. |
| (3) | Web container | Threads | Maximum number of threads that concurrently process requests on a J2EE server. |
| (4) | EADs client | Connection pool size | Pool size of the connection that is used to communicate with the EADs server. |
| (5) | EADs server | Number of maximum concurrent connections | Maximum number of concurrent connections to the EADs server. |
| (6) | Number of maximum concurrent executions | Maximum number of threads that concurrently process requests on the EADs server. | |
| (7) | Connection pool size | Pool size of the connection that is used to communicate with other EADs servers in the EADs cluster. |
The following table describes the settings for the number of concurrent connections, number of concurrent executions, and connection pool size recommended in the case of Figure 7-3:
Table 7-8 Recommended settings of number of concurrent connections, number of concurrent executions, and connection pool size
| Setting point | Recommended settings of number of concurrent connections, number of concurrent executions, and connection pool size | Impact if you do not set the recommended settings of number of concurrent connections, number of concurrent executions and, connection pool size |
|---|---|---|
| (1) - (3) | -- | -- |
| (4) | The same value as (3) | If you specify a value that is smaller than the recommended value, pooled connections become insufficient because the J2EE server threads are exceeded. As a result, connections might get established and broken whenever there is a request. |
| (5) | (1) |
If you specify a value that is smaller than the recommended value, connections with the EADs server fail because the maximum number of concurrent connections to the EADs server are exceeded. As a result, global session operations on the EADs server might fail. |
| (6) | The same value as (5) | -- |
| (7) | (6) |
If you specify a value that is smaller than the recommended value, pooled connections become insufficient because of access concentration from EADs clients and other EADs servers. As a result, connections might get established and broken whenever there is a request. |
All Rights Reserved. Copyright (C) 2013, 2015, Hitachi, Ltd.