uCosminexus Application Server, Web Container Functionality Guide

[Contents][Glossary][Index][Back][Next]

5.8.2 Execution environment settings (J2EE server settings)

To use controlling of communication by the persistent connection, you must set up the J2EE server.

This subsection describes the settings and examples for controlling communication by the persistent connection.

Organization of this subsection
(1) Setting up the J2EE server
(2) Example settings

(1) Setting up the J2EE server

Implement the J2EE server settings in the Easy Setup definition file. Specify the definition for controlling communication by the persistent connection in the <configuration> tag of the logical J2EE server (j2ee-server) in the Easy Setup definition file.

The following table lists the definitions in the Easy Setup definition file for controlling communication by the persistent connection.

Table 5-13 Definitions in the Easy Setup definition file for controlling communication by persistent connection

Parameter to be specified Setting contents
webserver.connector.inprocess_http.persistent_connection.max_connections Specifies the upper limit for the number of persistent connections to control the number of Web clients that can process requests continuously with one TCP connection.
webserver.connector.inprocess_http.persistent_connection.max_requests Specifies the upper limit for the request processing frequency of the persistent connection to control the processing when there are continuous requests from the same Web client.
webserver.connector.inprocess_http.persistent_connection.timeout Specifies the timeout value for persistent connection to control the request waiting time of the persistent connection.

For details on the Easy Setup definition file and the parameters to be specified, see the uCosminexus Application Server Definition Reference Guide.

(2) Example settings

The following is an example of settings for controlling communication by the persistent connection:

 
...
<param>
 
<param-name>webserver.connector.inprocess_http.persistent_connection.max_connections</param-name>
 <param-value>5</param-value>
</param>
<param>
 
<param-name>webserver.connector.inprocess_http.persistent_connection.max_requests</param-name>
 <param-value>100</param-value>
</param>
<param>
 
<param-name>webserver.connector.inprocess_http.persistent_connection.timeout</param-name>
 <param-value>15</param-value>
</param>
...
 

In this example, when the number of TCP connections exceeds '5' or when the request processing frequency exceeds 100, the TCP connection disconnects after the processing of the request ends. Also, if there is no request to process requests even after the timeout period of 15 seconds passes, the TCP connection disconnects.