7-8 Performance and Tuning for Oracle WebLogic Server
1.
Configure multiple network channels using different IP and port settings. See Configure custom network channels in Oracle WebLogic Server Administration
Console Help.
2.
In your client-side code, use a JNDI URL pattern similar to the pattern used in clustered environments. The following is an example for a client using two
network channels:
t3:ip1:port1,ip2:port2 See Understanding Network Channels in Configuring Server Environments for Oracle
WebLogic Server.
7.5.6 Reducing the Potential for Denial of Service Attacks
To reduce the potential for Denial of Service DoS attacks while simultaneously optimizing system availability, WebLogic Server allows you to specify the following
settings:
■
Maximum incoming message size
■
Complete message timeout
■
Number of file descriptors UNIX systems For optimal system performance, each of these settings should be appropriate for the
particular system that hosts WebLogic Server and should be in balance with each other, as explained in the sections that follow.
7.5.6.1 Tuning Message Size
WebLogic Server allows you to specify a maximum incoming request size to prevent server from being bombarded by a series of large requests. You can set a global value
or set specific values for different protocols and network channels. Although it does not directly impact performance, JMS applications that aggregate messages before
sending to a destination may be refused if the aggregated size is greater than specified value. See Servers: Protocols: General in Oracle WebLogic Server Administration Console
Help and
Section 14.15, Tuning Applications Using Unit-of-Order .
7.5.6.2 Tuning Complete Message Timeout
Make sure that the complete message timeout parameter is configured properly for your system. This parameter sets the maximum number of seconds that a server waits
for a complete message to be received.
The default value is 60 seconds, which applies to all connection protocols for the default network channel. This setting might be appropriate if the server has a number
of high-latency clients. However, you should tune this to the smallest possible value without compromising system availability.
If you need a complete message timeout setting for a specific protocol, you can alternatively configure a new network channel for that protocol.
For information about displaying the Administration Console page from which the complete message timeout parameter can be set, see Configure protocols in the
Oracle WebLogic Server Administration Console Help.
7.5.6.3 Tuning Number of File Descriptors
On UNIX systems, each socket connection to WebLogic Server consumes a file descriptor. To optimize availability, the number of file descriptors for WebLogic
Tuning WebLogic Server 7-9
Server should be appropriate for the host machine. By default, WebLogic Server configures 1024 file descriptors. However, this setting may be low, particularly for
production systems.
Note that when you tune the number of file descriptors for WebLogic Server, your changes should be in balance with any changes made to the complete message timeout
parameter. A higher complete message timeout setting results in a socket not closing until the message timeout occurs, which therefore results in a longer hold on the file
descriptor. So if the complete message timeout setting is high, the file descriptor limit should also be set high. This balance provides optimal system availability with
reduced potential for denial-of-service attacks.
For information about how to tune the number of available file descriptors, consult your UNIX vendor’s documentation.
7.5.7 Tune the Chunk Parameters
