WAS v8.5 > Reference > Custom properties

HTTP transport custom properties panel

HTTP transports are used for mixed cell nodes with a version prior to v6.x. If we are using nodes from a version prior to v6.x, and we have the script compatibility mode enabled, we will see this option. If we have no nodes with version prior to v6.x, we will not seen this option.

To handle HTTP requests on v6.x notes and above use HTTP transport channels instead of HTTP transports.

The use of IPv6 (Internet Protocol v6) and WS-AT (Web Services Atomic Transactions) are not supported on HTTP transports; they are only supported on HTTP transport channel chains.

If we are using HTTP transports, we can set the following custom properties on either the web container or HTTP transport custom properties page on the dmgr console. 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.

To specify custom properties for a specific transport on the HTTP transport using the dmgr console

Enter the property to configure in the Name field and the value to set it to in the Value field.

Click Save and restart the server.

Following is a list of custom properties provided with the product. These properties are not shown on the settings page for an HTTP transport.


ConnectionIOTimeOut

Use the ConnectionIOTimeOut property to specify how long the J2EE server waits for an I/O operation to complete. Set this variable for each of the HTTP transport definitions on the server. You will need to set this variable for both SSL transport and non-SSL transport. Specifying a value of zero disables the time out function.
Information Value
Data type Integer
Default

5 seconds for the IBM i and distributed platforms


ConnectionKeepAliveTimeout

Use the ConnectionKeepAliveTimeout property to specify the maximum number of seconds to wait for the next request on a keep alive connection.
Information Value
Data type Integer
Default

5 seconds for the IBM i and distributed platforms


KeepAliveEnabled

This property is only valid for IBM i and distributed platforms. Use the KeepAliveEnabled property to specify whether or not to keep connections alive.
Information Value
Data type String
Value true or false
Default true


MaxConnectBacklog

This property is only valid for IBM i and distributed platforms. Use the MaxConnectBacklog property to specify the maximum number of outstanding connect requests the operating system will buffer while it waits for the application server to accept the connections. If a client attempts to connect when this operating system buffer is full, the connect request will be rejected.

Keep in mind that a single client browser might need to open multiple concurrent connections (perhaps 4 or 5); however, also keep in mind that increasing this value consumes more kernel resources. The value of this property is specific to each transport.
Information Value
Data type Integer
Default 511


MaxKeepAliveConnections

This property is only valid for IBM i and distributed platforms. It is ignored on the z/OS platform because asynchronous I/O sockets are used to maintain connections in that environment. Use the MaxKeepAliveConnections property to specify the maximum number of concurrent keep alive (persistent) connections across all HTTP transports. To make a particular transport close connections after a request, we can set MaxKeepAliveConnections to 0 (zero), or we can set KeepAliveEnabled to false on that transport.

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 might 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:

Information Value
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 there are threads available to handle new incoming connect requests.


MaxKeepAliveRequests

Use the MaxKeepAliveRequests property to specify 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.

On the IBM i and distributed platforms, when this property is set to 0 (zero), the connection stays open as long as the application server is running.
Information Value
Data type Integer
Default

100 requests for the IBM i and distributed platforms


RemoveServerHeader

Specify whether an existing server header is removed before a response message is sent. If true, the value specified for the ServerHeaderValue property is ignored.
Information Value
Data type String
Value true or false
Default false

This custom property takes effect on the web container level only. We cannot set it on the transport level. To set this custom property, see Modifying the default web container configuration.


ResponseBufferSize

Specify, in bytes, the default size of the initial buffer allocation for the response buffer. When the buffer fills up, a flush for this buffer space will automatically occur. If a value is not specified for this property, the default response buffer size of 32K bytes is used.

The setBufferSize() API method can be used to override the value specified for this custom property at the individual servlet level.
Information Value
Data type Integer
Default 32000 bytes


ServerHeaderValue

Specify a server header this is added to outgoing response messages if server header is not already provided. This property is ignored if the RemoveServerHeader property is set to true.
Information Value
Data type string
Default WAS/x.x

x.x is the version of WAS that you are using.

This custom property takes effect on the web container level only. We cannot set it on the transport level. To set this custom property, see Modifying the default web container configuration.


SoLingerValue

Specify, in seconds, the amount, the socket close operation waits for data contained in the TCP/IP send buffer to be sent. This property is ignored if the UseSoLinger property is set to false.
Information Value
Data type Integer
Default 20 seconds


TcpNoDelay

Set the socket TCP_NODELAY option which enables and disables the use of the TCP Nagle algorithm for connections received on this transport. When true, use of the Nagle algorithm is disabled.
Information Value
Data type String
Value true or false
Default true


Trusted

Use the Trusted property to indicate the application server can use the private headers the web server plug-in adds to requests.
Information Value
Data type String
Value true or false
Default false

This property must be set to false for Secure Sockets Layer (SSL) client certificate authentication to work.


UseSoLinger

Set the socket SO_LINGER option. This property configures whether the socket close operation waits until all of the data contained in the TCP/IP send buffer is sent before closing a connection. If true, and the time expires before the all of the content of the send buffer sent, any data remaining in the send buffer is lost.

The SoLingerValue property is ignored if this property is set to false.
Information Value
Data type String
Value true or false
Default true


Related

Modify the default web container configuration
Tune the application serving environment
HTTP transport custom properties for web services applications
Administrative console page features
HTTP Tunnel transport channel custom properties
Web container custom properties


+

Search Tips   |   Advanced Search