Table 54-1 NetworkChannelMBean Element Attributes
|
Attribute
|
Description
|
Range of Values and Default
|
Console Label
|
|
Accept-Backlog
|
Allowed backlog of connection requests on the listen port(s). Individual servers may override this value using a NetworkAccessPointMBean. Setting the backlog to 0 may prevent accepting any incoming connection on some of the OS.
|
Default: 50
Minimum: 0
|
Accept Backlog
|
|
Bound-Outgoing-Enabled
|
Bind new outgoing server side T3 or T3S connections to the server channel's listen address. Other protocols ignore this field. This field is ignored for connections initiated via URLs, it takes effect if and only if the connection was initiated by accessing a remote reference (such as an EJB or RMI stub.)
|
Default: false
|
Bound Outgoing Enabled
|
|
COMEnabled
|
Whether or not plaintext (non-SSL) COM traffic is enabled.
|
Default: false
|
COM Enabled
|
|
Channel-Weight
|
A weight to give this channel when creating server-to-server connections.
|
Default: 50
Minimum: 1
Maximum: 100
|
Channel Weight
|
|
Cluster-Address
|
This channel's cluster address. If this is not set, the cluster address from the cluster configuration is used in its place.
|
Default: null
|
Cluster Address
|
|
Complete-COMMessage-Timeout
|
The maximum number of seconds spent waiting for a complete COM message to be received. This attribute helps guard against denial of service attacks in which a caller indicates that they will be sending a message of a certain size which they never finish sending. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 60
Minimum: 0
Maximum: 480
Units: seconds
|
Complete COM Message Timeout
|
|
Complete-HTTPMessage-Timeout
|
The maximum number of seconds spent waiting for a complete HTTP message to be received. This attribute helps guard against denial of service attacks in which a caller indicates that they will be sending a message of a certain size which they never finish sending. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 60
Minimum: 0
Maximum: 480
Units: seconds
|
Complete HTTP Message Timeout
|
|
Complete-T3Message-Timeout
|
The maximum number of seconds spent waiting for a complete T3 message to be received. This attribute helps guard against denial of service attacks in which a caller indicates that they will be sending a message of a certain size which they never finish sending. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 60
Minimum: 0
Maximum: 480
Units: seconds
|
Complete T3 Message Timeout
|
|
Deployment-Order
|
A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all startup classes before it prioritizes and deploys EJBs.
Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.
|
Default: 1000
Minimum: 0
Maximum: 2147483647
|
Deployment Order
|
|
Description
|
Optional short description of this channel for console display purposes. For long descriptions, use the "Notes" field.
|
Default: null
|
Description
|
|
HTTPEnabled
|
Whether or not plaintext (non-SSL) HTTP traffic is enabled.
|
Default: false
|
HTTP Enabled
|
|
HTTPSEnabled
|
Whether or not secure (SSL) HTTP traffic is enabled.
|
Default: false
|
HTTPS Enabled
|
|
Listen-Port
|
The plaintext (non-SSL) listen port for the channel. Individual servers may override this value, but may not enable the port if disabled here and may not disable the port if enabled here. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 8001
Minimum: 1
Maximum: 65534
|
Listen Port
|
|
Listen-Port-Enabled
|
Whether or not plaintext port is enabled for the channel.
|
Default: false
|
Listen Port Enabled
|
|
Login-Timeout-Millis
|
The login timeout for the server, in milliseconds. This value must be equal to or greater than 0. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 5000
Minimum: 0
Maximum: 100000
Units: milliseconds
|
Login Timeout
|
|
Login-Timeout-Millis-SSL
|
The number of milliseconds that WebLogic Server waits for an SSL connection before timing out. SSL connections take longer to negotiate than regular connections. If clients are connecting over the Internet, raise the default number to accommodate additional network latency. A value of 0 disables the attribute.
Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 25000
Minimum: 0
Maximum: 2147483647
Units: milliseconds
|
SSL Login Timeout
|
|
Max-COMMessage-Size
|
The maximum COM 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. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 10000000
Minimum: 4096
Maximum: 2000000000
Units: bytes
|
Max COM Message Size
|
|
Max-HTTPMessage-Size
|
The maximum HTTP 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. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 10000000
Minimum: 4096
Maximum: 2000000000
Units: bytes
|
Max HTTP Message Size
|
|
Max-T3Message-Size
|
The maximum T3 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. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 10000000
Minimum: 4096
Maximum: 2000000000
Units: bytes
|
Max T3 Message Size
|
|
Name
|
The name of the channel. The name must not start with ".WL".
|
|
Name
|
|
Notes
|
Optional information that you can include to describe this configuration.
|
|
Notes
|
|
Outgoing-Enabled
|
Whether or not new server-to-server connections may consider this channel when initiating.
|
Default: true
|
Outgoing Enabled
|
|
SSLListen-Port
|
The SSL listen port for the channel. Individual server's may override this value, but may not enable the port if disabled here and may not disable the port if enabled here. SSL must be configured and enabled for this port to work. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 8002
Minimum: 1
Maximum: 65534
|
SSL Listen Port
|
|
SSLListen-Port-Enabled
|
Whether or not SSL port is enabled for the channel. SSL must be configured and enabled in addition to this setting for the SSL port to work.
|
Default: false
|
SSL Listen Port Enabled
|
|
T3Enabled
|
Whether or not plaintext (non-SSL) T3 traffic is enabled. Note that it is not possible to disable T3 traffic on the default channel(s).
|
Default: false
|
T3 Enabled
|
|
T3SEnabled
|
Whether or not secure T3 traffic is enabled. Note that it is not possible to disable T3 traffic on the default channel(s).
|
Default: false
|
T3S Enabled
|
|
Targets
|
The targets in the current domain on which this item can be deployed.
|
|
Targets
|
|
Tunneling-Client-Ping-Secs
|
Interval (in seconds) at which to ping an http-tunneled client to see if its still alive. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 45
Units: seconds
|
Tunneling Client Ping
|
|
Tunneling-Client-Timeout-Secs
|
Duration (in seconds) after which a missing http-tunneled client is considered dead. Individual servers may override this value using a NetworkAccessPointMBean.
|
Default: 40
Units: seconds
|
Tunneling Client Timeout
|
|
Tunneling-Enabled
|
Enables tunneling via http.
|
Default: false
|
Tunneling Enabled
|
