Table 1-41
Attribute Label
|
Description
|
Value Constraints
|
Complete Message Timeout
|
The maximum number of seconds that this server waits for a complete message to be received. This attribute helps guard against denial of service attacks in which a caller indicates that it will be sending a message of a certain size which it never finishes sending.
If you configure a network channel for this server, you can override this getCompleteMessageTimeout value and specify a different value for the network channel.
MBean: weblogic.management. configuration.ServerMBean
Attribute: CompleteMessageTimeout
|
Units: seconds
Minimum: 0
Maximum: 480
Default: 60
Configurable: yes
Dynamic: yes
|
Idle Connection Timeout
|
The maximum number of seconds that a connection is allowed to be idle before it is closed by the server. This attribute helps guard against server deadlock through too many open connections. The T3 and T3S protocols ignore this attribute.
If you configure a network channel for this server, you can override this getIdleConnectionTimeout value and specify a different value for the network channel.
MBean: weblogic.management. configuration.ServerMBean
Attribute: IdleConnectionTimeout
|
Units: seconds
Minimum: 0
Default: 65
Configurable: yes
Dynamic: yes
|
Enable Tunneling
|
Enables tunneling for the T3, T3S, HTTP, HTTPS, IIOP, and IIOPS protocols. If you create network channels for this server, each channel can override this setting.
MBean: weblogic.management. configuration.ServerMBean
Attribute: TunnelingEnabled
|
Default: false
Valid values:
Dynamic: yes
|
Tunneling Client Ping
|
Interval (in seconds) at which to ping a tunneled client to see if it is still alive.
MBean: weblogic.management. configuration.ServerMBean
Attribute: TunnelingClientPingSecs
|
Units: seconds
Minimum: 1
Default: 45
Dynamic: yes
|
Tunneling Client Timeout
|
Duration (in seconds) after which a missing tunneled client is considered dead.
MBean: weblogic.management. configuration.ServerMBean
Attribute: TunnelingClientTimeoutSecs
|
Units: seconds
Minimum: 1
Default: 40
Dynamic: yes
|
Maximum Message Size
|
The maximum message size allowable in a message header. This attribute attempts to prevent a denial of service attack whereby a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests.
If you configure a network channel for this server, you can override this attribute value and specify a different value for the network channel.
MBean: weblogic.management. configuration.ServerMBean
Attribute: MaxMessageSize
|
Units: bytes
Minimum: 4096
Maximum: 2000000000
Default: 10000000
Configurable: yes
Dynamic: yes
|