BEA WebLogic Server Tuning Guide

17
if (numReaders > numSockets)
timeout = SocketReaderTimeoutMaxMillis
else
Timeout = numReaders * 60000 / numSockets
if (timeout < SocketReaderTimeoutMinMillis)
timeout = SockerReaderTimeoutMinMillis
if (timeout > SocketReaderTimeoutMaxMillis)
timeout = SockerReaderTimeoutMaxMillis
SocketReaderTimeoutMinMillis and SocketReaderTimeoutMaxMillis are by default set to 100 and 500, respectively,
but can be overridden in the Server element.
The attributes of the Server object, SocketReaderTimeoutMinMillis and SockerReaderTimeoutMaxMillis can be used
to control the polling timeout in the server. If there are enough socket readers in the Execute queue such that the
number of socket readers is greater than or equal to the average number of open sockets on the server, set the
SocketReaderTimeoutMaxMillis to a high value (for example, 2 or 3 seconds). This helps reduce the number of
polling activities on a socket before a request is read.
If the number of socket readers is less than the number of active sockets, WebLogic Server writes a warning
message in the server log file. When the number of socket readers is less than the average number of socket
readers, the SocketReaderTimeoutMaxMillis can be set to the default value of 500 milliseconds.
Note that when the number of socket readers is less than the number of open sockets, an alert is written to the
WebLogic Server log file. This log file can be periodically monitored and, if needed, the number of socket readers
configured can be increased.
For example, consider a WebLogic Server instance with 10 socket reader threads and 30 active sockets. In this
scenario:
numReaders = 10
numSockets = 30
timeout = 10 * 60000/30 = 10 * 2000 = 20000 milliseconds.
Since the timeout value (20000) is greater than the default maximum (which is 500), the default maximum is used.
3.11 Configuring TCP/IPV6-related Parameters
WebLogic Server on Guardian requires TCP/IPV6 stack configured in INET4 mode. This section describes
configuration options needed for TCP/IPV6.
3.12 Setting the TCP/IP Process Name
TCP/IPV6 cannot be configured as the default TCP/IP process on a NonStop server. The Guardian define name
=TCPIP^PROCESS^NAME can be used to make TCP/IPV6 stack the default stack of an application.
The following command sets the define =TCPIP^PROCESS^NAME to a TCP/IP provider named $ZSM1:
$ add_define =TCPIP^PROCESS^NAME class=map file=\$ZSM1
Once TCP/IPV6 is specified as the TCP stack used by the WebLogic Server process, an additional define must be
specified (=PTCPIP^FILTER^KEY) so that multiple WebLogic Server processes can join a multicast socket group.