Table 19-1 IIOP attributes
Attribute
|
Description
|
Range of Values and Default
|
CompleteMessageTimeout
|
Deprecated. Specify the maximum number of seconds spent waiting for a complete IIOP 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.
|
Units: seconds
Default: -1
Minimum: 0
Maximum: 480
|
DefaultCharCodeset
|
Specify what codeset should be used for the default native character codeset. This is required to interoperate with some Orbs that do not do codeset negotiation, or do it incorrectly. Setting this to anything other than US-ASCII will cause failure against JDK 1.3.1 clients.
|
Admin Console field label: Default Char Codeset
Required: no
Default: US-ASCII
|
DefaultMinorVersion
|
Specify the default minor GIOP version for IIOP messages. This attribute is useful for client orbs with broken GIOP 1.2 implementations.
|
Admin Console field label: Default GIOP Version
Default: 2
Minimum: 0
Maximum: 2
|
DefaultWideCharCodeset
|
Specify what codeset should be used for the default native wide character codeset. This is required to interoperate with some Orbs that do not do codeset negotiation, or do it incorrectly. Setting this to anything other than UCS-2 will cause failure against JDK 1.3.1 clients.
|
Admin Console field label: Default Wide Char Codeset
Required: no
Default: UCS-2
|
IdleConnectionTimeout
|
Specify the maximum number of seconds an IIOP 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.
|
Units: seconds
Default: -1
Minimum: 0
|
MaxMessageSize
|
Deprecated. Specify the maximum IIOP 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.
|
Units: bytes
Default: -1
Minimum: 4096
Maximum: 2000000000
|
Name
|
The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.
|
Required: no
|
Notes
|
Optional information that you can include to describe this configuration.
|
Required: no
|
TxMechanism
|
Specify whether IIOP should use the WebLogic-specific JTA to propagate transactions or the OMG-specified OTS. It is not possible to use both since it affects the way transactions are negotiated.
|
Admin Console field label: Transaction Mechanism
Required: no
Default: OTS
|