1. RESTful Edit Management Interface for Oracle WebLogic Server
  2. Tasks
  3. JTA Cluster

Modify This JTA Cluster

post

/management/weblogic/{version}/edit/clusters/{name}/JTACluster

Modify this JTA cluster.

Request

Supported Media Types
Path Parameters
Header Parameters
  • The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.
Body ()

Must contain the modified JTA cluster model.

Root Schema : JTA Cluster
Type: object
Show Source
  • Minimum Value: 1
    Maximum Value: 2147483647

    Specifies the maximum amount of time, in seconds, a transaction manager persists in attempting to complete the second phase of a two-phase commit transaction.

    During the second phase of a two-phase commit transaction, the transaction manager continues to try to complete the transaction until all resource managers indicate that the transaction is completed. After the abandon transaction timer expires, no further attempt is made to resolve the transaction. If the transaction is in a prepared state before being abandoned, the transaction manager rolls back the transaction to release any locks held on behalf of the abandoned transaction.

  • Minimum Value: 1
    Maximum Value: 2147483647

    The maximum number of cycles that the transaction manager performs the beforeCompletion synchronization callback for this cluster.

    Nothing prevents a Synchronization object from registering another during beforeCompletion, even those whose beforeCompletions have already been called. For example, an EJB can call another in its ejbStore() method. To accommodate this, the transaction manager calls all Synchronization objects, then repeats the cycle if new ones have been registered. This count sets a limit to the number of cycles that synchronization occurs.

  • Minimum Value: 10
    Maximum Value: 1800

    The interval at which the transaction manager creates a new transaction log file and checks all old transaction log files to see if they are ready to be deleted.

  • Default Value: false

    Indicates that cluster-wide recovery is used for distributed transactions.

    When enabled, recovery operations for a distributed transaction are applied to all the servers of the cluster hosting a InterposedTransactionManager rather than just the server hosting the InterposedTransactionManager.

  • Minimum Value: -1
    Maximum Value: 2147483647

    Specifies the maximum amount of time, in seconds, a transaction manager waits for all resource managers to respond and indicate if the transaction can be committed or rolled back.

    • The default value is 0, which sets the value to approximately twice the default transaction-timeout value with a maximum value of 120 seconds. This value provides backward compatibility for prior releases without this setting.

    • If the specified value is -1, the maximum value supported by this attribute is used.

    • If the specified value exceeds the value set for abandon-timeout-seconds, the value of abandon-timeout-seconds is used.

  • Items
    Title: Items
    Read Only: true

    Returns a list of one or more transaction resources (determiners). A determiner's in-doubt transaction records are used during transaction recovery when a TLog is not present.

  • Items
    Title: Items

    Specifies a list of one or more transaction resources (determiners) separated by line breaks. A determiner's in-doubt transaction records are used during transaction recovery when a TLog is not present.

  • Read Only: true
    Default Value: false

    Return whether the MBean was created dynamically or is persisted to config.xml

  • Specifies whether the transaction manager automatically performs an XA Resource forget operation for heuristic transaction completions.

    When enabled, the transaction manager automatically performs an XA Resource forget() operation for all resources as soon as the transaction learns of a heuristic outcome. Disable this feature only if you know what to do with the resource when it reports a heuristic decision.

  • Read Only: true

    Return the unique id of this MBean instance

  • Minimum Value: 10
    Maximum Value: 2147483647

    Maximum number of concurrent requests to resources allowed for each server.

  • Minimum Value: 0
    Maximum Value: 9.223372036854776E18

    Maximum duration time, in milliseconds, that a resource is declared dead. After the duration, the resource is declared available again, even if the resource provider does not explicitly re-register the resource.

  • Minimum Value: 0
    Maximum Value: 2147483647
    Default Value: 300

    The maximum amount of time, in seconds, WebLogic Server waits for the determiner to recover from a failure. If the determiner does not recover after this period, WebLogic Server sets the TLog health state to HEALTH_FAILED.

  • Minimum Value: 1
    Maximum Value: 2147483647

    The maximum number of simultaneous in-progress transactions allowed on a server in this cluster.

  • Minimum Value: 1000
    Maximum Value: 9.223372036854776E18

    The interval for which the transaction map must be full for the JTA subsystem to declare its health as CRITICAL.

  • Minimum Value: 0
    Maximum Value: 2147483647

    The maximum number of unique transaction names for which statistics are maintained.

    The first 1001 unique transaction names are maintained as their own transaction name and stored in each statistic. After the 1001st transaction name is reached, the transaction name is stored as weblogic.transaction.statistics.namedOverflow, and the transaction statistic is also merged and maintained in weblogic.transaction.statistics.namedOverflow

    A transaction name typically represents a category of business transactions, such as "funds-transfer."

  • Minimum Value: 0
    Maximum Value: 9.223372036854776E18

    Maximum allowed time duration, in milliseconds, for XA calls to resources. If a particular XA call to a resource exceeds the limit, the resource is declared unavailable.

  • Minimum Value: 1
    Maximum Value: 2147483647

    The time interval, in seconds, that the checkpoint is done for the migrated transaction logs (TLOGs).

  • Read Only: true

    The user-specified name of this MBean instance.

    This name is included as one of the key properties in the MBean's javax.management.ObjectName

    Name=user-specified-name

    Constraints

    • legal null

  • Optional information that you can include to describe this configuration.

    WebLogic Server saves this note in the domain's configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the xml entity <. Carriage returns/line feeds are preserved.

    Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

  • The dispatch policy to use when performing XA operations in parallel.

  • Indicates that XA calls are executed in parallel if there are available threads.

  • Minimum Value: 0
    Maximum Value: 2147483647

    The interval that a particular resource must be accessed within for it to be included in the checkpoint record.

  • Minimum Value: 60000
    Maximum Value: 9.223372036854776E18

    The interval that recovery is attempted until the resource becomes available.

  • Specifies the security mode of the communication channel used for XA calls between servers that participate in a global transaction. All server instances in a domain must have the same security mode setting.

    Security Interoperability Mode options:

    • default The transaction coordinator makes calls using the kernel identity over an admin channel if it is enabled, and anonymous otherwise. Man-in-the-middle attacks are possible if the admin channel is not enabled.

    • performance The transaction coordinator makes calls using anonymous at all times. This implies a security risk since a malicious third party could then try to affect the outcome of transactions using a man-in-the-middle attack.

    • compatibility The transaction coordinator makes calls as the kernel identity over an insecure channel. This is a high security risk because a successful man-in-the-middle attack would allow the attacker to gain administrative control over both domains. This setting should only be used when strong network security is in place.

  • Minimum Value: 0

    The time interval, in milliseconds, at which internal objects used to serialize resource enlistment are cleaned up.

  • Default Value: 180

    Indicates how long the server should wait for active transactions to complete before allowing shutdown.

  • Items
    Title: Items

    Return all tags on this Configuration MBean

  • Default Value: false

    Indicates tight coupling of transaction branches that span different transaction manager systems.

    When enabled, WebLogic uses the transaction identifier of a transaction imported by the InterposedTransactionManager for XA calls rather than an internally mapped Xid. This applies to inter-domain WebLogic transactions and transactions imported from Tuxedo. This allows for tight coupling of transaction branches for transactions that span across different transaction manager systems.

    If a transaction between WebLogic and Tuxedo resources uses a GridLink Data Source with GridLink Affinity enabled, the XA Affinity context is automatically used for the transaction.

  • Minimum Value: 1
    Maximum Value: 2147483647

    Specifies the maximum amount of time, in seconds, an active transaction is allowed to be in the first phase of a two-phase commit transaction. If the specified amount of time expires, the transaction is automatically rolled back.

  • Default Value: false

    Indicates two-phase transaction recovery logs are written even if one or more determiners are configured.

  • Indicates that the two-phase commit protocol is used to coordinate transactions across two or more resource managers.

    If not selected:

    • Two-phase commit is disabled and any attempt to use two-phase commit results in a RollbackException being thrown.

    • All transaction logging is disabled, including checkpoint records.

  • Read Only: true

    Returns the type of the MBean.

    Constraints

    • unharvestable
  • Minimum Value: 0
    Maximum Value: 2147483647

    The amount of time, in seconds, a transaction manager waits for transactions involving the resource to complete before unregistering a resource. This grace period helps minimize the risk of abandoned transactions because of an unregistered resource, such as a JDBC data source module packaged with an application.

    During the specified grace period, the unregisterResource call blocks until the call returns and no new transactions are started for the associated resource. If the number of outstanding transactions for the resource goes to , the unregisterResource call returns immediately.

    At the end of the grace period, if outstanding transactions are associated with the resource, the unregisterResource call returns and a log message is written to the server on which the resource was previously registered.

  • Items
    Title: Items

    Returns the domains for which non-secure protocols should be used for internal JTA communication if the servers in the domains are configured to use network channels.

  • Items
    Title: Items

    Returns the remote domains for which public addresses should be used if the servers in the domains are configured to use network channels for internal JTA communication.

  • Default Value: false

    Specifies whether to use issuedtoken to enable authentication between the WS-AT coordinator and participant.

  • Default Value: SSLNotRequired
    Allowed Values: [ "SSLNotRequired", "SSLRequired", "ClientCertRequired" ]

    Specifies transport security mode required by WebService Transaction endpoints.

    Transport Security options:

    • SSLNotRequired All WebService Transaction protocol messages are exchanged over the HTTP channel.

    • SSLRequired All WebService Transaction protocol messages are and can only be exchanged over the HTTPS.

    • ClientCertRequired All WebService Transaction protocol messages are and can only be exchanged over the HTTPS, and WLS enforces the presence of client certificate

Nested Schema : Items
Type: array
Title: Items
Read Only: true

Returns a list of one or more transaction resources (determiners). A determiner's in-doubt transaction records are used during transaction recovery when a TLog is not present.

Show Source
Nested Schema : Items
Type: array
Title: Items

Specifies a list of one or more transaction resources (determiners) separated by line breaks. A determiner's in-doubt transaction records are used during transaction recovery when a TLog is not present.

Show Source
Nested Schema : Items
Type: array
Title: Items

Return all tags on this Configuration MBean

Show Source
Nested Schema : Items
Type: array
Title: Items

Returns the domains for which non-secure protocols should be used for internal JTA communication if the servers in the domains are configured to use network channels.

Show Source
Nested Schema : Items
Type: array
Title: Items

Returns the remote domains for which public addresses should be used if the servers in the domains are configured to use network channels for internal JTA communication.

Show Source
Nested Schema : Determiner Candidate Resource Info V
Type: object
Show Source
Security
  • Type: basic
    Description: A user in the Admin security role.
Back to Top

Response

200 Response

Back to Top