67 lines
5.2 KiB
HTML
67 lines
5.2 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Example: Setting custom properties for an HTTP transport</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h3><a name="admcpex"></a>Example: Setting custom properties for an HTTP transport</h3>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express has several transport properties that are not shown in the WebSphere administrative console in the settings page for an HTTP transport. They are as follows:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><p><strong>ConnectionIOTimeout</strong>
|
||
|
|
<br>Specifies the maximum number of seconds to wait when trying to read or process data during a request. Data type: Integer.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>ConnectionKeepAliveTimeout</strong>
|
||
|
|
<br>Specifies the maximum number of seconds to wait for the next request on a keep-alive connection. Data type: Integer.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>MaxKeepAliveConnections</strong>
|
||
|
|
<br>Specifies the maximum number of concurrent keep-alive (persistent) connections across all HTTP transports. To make a particular transport close connections after a request, you can set MaxKeepAliveConnections to <tt>0</tt> (zero) or you can set KeepAliveEnabled to <tt>false</tt> on that transport.</p>
|
||
|
|
|
||
|
|
<p>The Web server plug-in keeps connections open to the application server as long as it can. However, if the value of this property is too small, performance is negatively impacted because the plug-in has to open a new connection for each request instead of sending multiple requests through one connection. The application server may not accept a new connection under a heavy load if there are too many sockets in TIME_WAIT state. If all client requests are going through the Web server plug-in and there are many TIME_WAIT state sockets for port 9080, the application server is closing connections prematurely, which decreases performance. The application server closes the connection from the plug-in, or from any client, for any of the following reasons:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>The client request was an HTTP 1.0 request when the Web server plug-in always sends HTTP 1.1 requests.</li>
|
||
|
|
<li>The maximum number of concurrent keep-alives was reached. A keep-alive must be obtained only once for the life of a connection, that is, after the first request is completed, but before the second request can be read.</li>
|
||
|
|
<li>The maximum number of requests for a connection was reached, preventing denial of service attacks in which a client tries to hold on to a keep-alive connection forever.</li>
|
||
|
|
<li>A time out occurred while waiting to read the next request or to read the remainder of the current request.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Data type: Integer. Default: 90% of the maximum number of threads in the Web container thread pool. This prevents all of the threads from being held by keep alive connections so that there are threads available to handle new incoming connect requests.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>MaxKeepAliveRequests</strong>
|
||
|
|
<br>Specifies the maximum number of requests which can be processed on a single keep alive connection. This parameter can help prevent denial-of-service attacks when a client tries to hold on to a keep-alive connection. The Web server plug-in keeps connections open to the application server as long as it can, providing optimum performance. Data type: Integer. Default: 100.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>KeepAliveEnabled</strong>
|
||
|
|
<br>Specifies whether to keep connections alive or not. Data type: Boolean. Default is <tt>true</tt>.</p>
|
||
|
|
<p>You can set these properties on either the Web Container or HTTP Transport Custom Properties pages. When set on the Web container Custom Properties page, all transports inherit the properties. Setting the same properties on a transport overrides like settings defined for a Web container.</p></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>To specify values for these custom properties for a specific transport on the HTTP Transport Custom Properties page:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><p>Access the settings page for transport properties in the WebSphere administrative console:</p>
|
||
|
|
<ol type="a">
|
||
|
|
<li>In the navigation menu, click <strong>Servers --> Application Servers --> <em>server</em> --> Web Container --> HTTP Transport</strong>, where <em>server</em> is the name of your application server.</li>
|
||
|
|
<li>Click the host whose properties you want to set.</li>
|
||
|
|
<li>Under <strong>Additional Properties</strong> click <strong>Custom Properties</strong>.</li>
|
||
|
|
<li>On the Custom Properties page, click <strong>New</strong>.</li>
|
||
|
|
</ol><p></p></li>
|
||
|
|
|
||
|
|
<li><p>On the settings page for a new property, enter the name of the transport property and the value to which you want it set. For example, if you want the transport to wait a maximum of 60 seconds when trying to read or write data during a request, enter <tt>ConnectionIOTimeout</tt> for the name and <tt>60</tt> for the value. Then click <strong>OK</strong>.</p></li>
|
||
|
|
|
||
|
|
<li><p>Click <strong>Save</strong> on the console taskbar and save the changes to the configuration.</p></li>
|
||
|
|
<li><p>Restart the server.</p></li>
|
||
|
|
<li><p>Regenerate the Web server plug-in.</p></li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|