Jump to

• Request
• Response

Modify This JDBCXA Params

post

/management/weblogic/{version}/edit/partitions/{name}/resourceGroups/{name}/JDBCSystemResources/{name}/JDBCResource/JDBCXAParams

Modify this JDBCXA params.

Request

Supported Media Types

• application/json

Path Parameters

• name: string
  The name property of the instance in the collection.
• version: string
  The version of the WebLogic REST interface.

Header Parameters

• X-Requested-By: string
  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 JDBCXA params model.

Root Schema : JDBCXA Params

Type: object

Show Source

• keepLogicalConnOpenOnRelease(optional): boolean
  Default Value: false

  Enables WebLogic Server to keep the logical JDBC connection open for a global transaction when the physical XA connection is returned to the connection pool.

  Select this option if the XA driver used to create database connections or the DBMS requires that a logical JDBC connection be kept open while transaction processing continues (although the physical XA connection can be returned to the connection pool).

  Only applies to data sources that use an XA driver.

  Use this setting to work around specific problems with JDBC XA drivers.

• keepXaConnTillTxComplete(optional): boolean
  Default Value: true

  Enables WebLogic Server to associate the same XA database connection from the connection pool with a global transaction until the transaction completes.

  Only applies to connection pools that use an XA driver.

  Use this setting to work around specific problems with JDBC XA drivers.

• needTxCtxOnClose(optional): boolean
  Default Value: false

  Specifies whether the XA driver requires a distributed transaction context when closing various JDBC objects (result sets, statements, connections, and so forth). Only applies to connection pools that use an XA driver.

  When enabled, SQL exceptions that are thrown while closing the JDBC objects without a transaction context will be suppressed.

  Use this setting to work around specific problems with JDBC XA drivers.

• newXaConnForCommit(optional): boolean
  Default Value: false

  Specifies that a dedicated XA connection is used for commit and rollback processing for a global transaction.

  Only applies to data sources that use an XA driver.

  Use this setting to work around specific problems with JDBC XA drivers.

• recoverOnlyOnce(optional): boolean
  Default Value: false

  Specifies that the transaction manager calls recover on the resource only once. Only applies to data sources that use an XA driver.

  Use this setting to work around specific problems with JDBC XA drivers.

• resourceHealthMonitoring(optional): boolean
  Default Value: true

  Enables JTA resource health monitoring for an XA data source. When enabled, if an XA resource fails to respond to an XA call within the period specified in MaxXACallMillis, WebLogic Server marks the data source as unhealthy and blocks any further calls to the resource.

  This property applies to XA data sources only, and is ignored for data sources that use a non-XA driver.

• xaRetryDurationSeconds(optional): integer(int32)
  Default Value: 0

  Determines the duration in seconds for which the transaction manager will perform recover operations on the resource. A value of zero indicates that no retries will be performed.

• xaRetryIntervalSeconds(optional): integer(int32)
  Default Value: 60

  The number of seconds between XA retry operations if XARetryDurationSeconds is set to a positive value.

• xaSetTransactionTimeout(optional): boolean
  Default Value: false

  Enables WebLogic Server to set a transaction branch timeout based on the value for XaTransactionTimeout.

  When enabled, the WebLogic Server Transaction Manager calls XAResource.setTransactionTimeout() before calling XAResource.start, and passes either the XA Transaction Timeout value or the global transaction timeout.

  You may want to set a transaction branch timeout if you have long-running transactions that exceed the default timeout value on the XA resource.

  Note: To use this feature, the resource manager (typically, the JDBC driver) must support the javax.transaction.xa.XAResource.setTransactionTimeout() method.

• xaTransactionTimeout(optional): integer(int32)
  Default Value: 0

  The number of seconds to set as the transaction branch timeout.

  If set, this value is passed as the transaction timeout value in the XAResource.setTransactionTimeout() call on the XA resource manager, typically the JDBC driver.

  When this value is set to , the WebLogic Server Transaction Manager passes the global WebLogic Server transaction timeout in seconds in the method.

  If set, this value should be greater than or equal to the global WebLogic Server transaction timeout.

  Note: You must enable XaSetTransactionTimeout to enable setting the transaction branch timeout.

{
    "type":"object",
    "properties":{
        "keepLogicalConnOpenOnRelease":{
            "default":false,
            "type":"boolean",
            "description":"<p>Enables WebLogic Server to keep the logical JDBC connection open for a global transaction when the physical XA connection is returned to the connection pool. </p><p>Select this option if the XA driver used to create database connections or the DBMS requires that a logical JDBC connection be kept open while transaction processing continues (although the physical XA connection can be returned to the connection pool).</p><p>Only applies to data sources that use an XA driver.</p><p>Use this setting to work around specific problems with JDBC XA drivers.</p>"
        },
        "keepXaConnTillTxComplete":{
            "default":true,
            "type":"boolean",
            "description":"<p>Enables WebLogic Server to associate the same XA database connection from the connection pool with a global transaction until the transaction completes.</p><p>Only applies to connection pools that use an XA driver.</p><p>Use this setting to work around specific problems with JDBC XA drivers.</p>"
        },
        "needTxCtxOnClose":{
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies whether the XA driver requires a distributed transaction context when closing various JDBC objects (result sets, statements, connections, and so forth). Only applies to connection pools that use an XA driver.</p><p>When enabled, SQL exceptions that are thrown while closing the JDBC objects without a transaction context will be suppressed.</p><p>Use this setting to work around specific problems with JDBC XA drivers.</p>"
        },
        "newXaConnForCommit":{
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies that a dedicated XA connection is used for commit and rollback processing for a global transaction.</p><p>Only applies to data sources that use an XA driver.</p><p>Use this setting to work around specific problems with JDBC XA drivers.</p>"
        },
        "recoverOnlyOnce":{
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies that the transaction manager calls recover on the resource only once. Only applies to data sources that use an XA driver.</p><p>Use this setting to work around specific problems with JDBC XA drivers.</p>"
        },
        "resourceHealthMonitoring":{
            "default":true,
            "type":"boolean",
            "description":"<p>Enables JTA resource health monitoring for an XA data source.  When enabled, if an XA resource fails to respond to an XA call within the period specified in MaxXACallMillis, WebLogic Server  marks the data source as unhealthy and blocks any further calls to the resource.</p><p> This property applies to XA data sources only, and is ignored for data sources that use a non-XA driver.</p>"
        },
        "xaRetryDurationSeconds":{
            "default":0,
            "type":"integer",
            "format":"int32",
            "description":"<p>Determines the duration in seconds for which the transaction manager will perform recover operations on the resource.  A value of zero indicates that no retries will be performed.</p>"
        },
        "xaRetryIntervalSeconds":{
            "default":60,
            "type":"integer",
            "format":"int32",
            "description":"<p>The number of seconds between XA retry operations if XARetryDurationSeconds is set to a positive value.</p>"
        },
        "xaSetTransactionTimeout":{
            "default":false,
            "type":"boolean",
            "description":"<p>Enables WebLogic Server to set a transaction branch timeout based on the value for XaTransactionTimeout.</p><p>When enabled, the WebLogic Server Transaction Manager calls <code>XAResource.setTransactionTimeout()</code> before calling <code>XAResource.start</code>, and passes either the XA Transaction Timeout value or the global transaction timeout. </p><p>You may want to set a transaction branch timeout if you have long-running transactions that exceed the default timeout value on the XA resource.</p><p><b>Note:</b> To use this feature, the resource manager (typically, the JDBC driver) must support the <code>javax.transaction.xa.XAResource.setTransactionTimeout()</code> method. </p>"
        },
        "xaTransactionTimeout":{
            "default":0,
            "type":"integer",
            "format":"int32",
            "description":"<p>The number of seconds to set as the transaction branch timeout.</p><p>If set, this value is passed as the transaction timeout value in the <code>XAResource.setTransactionTimeout()</code> call on the XA resource manager, typically the JDBC driver. </p><p>When this value is set to <code></code>, the WebLogic Server Transaction Manager passes the global WebLogic Server transaction timeout in seconds in the method.</p><p>If set, this value should be greater than or equal to the global WebLogic Server transaction timeout.</p><p><b>Note:</b> You must enable XaSetTransactionTimeout to enable setting the transaction branch timeout.</p>"
        }
    },
    "description":""
}

Security

• Admin: basic
  Type: basic

  Description: A user in the Admin security role.
• Deployer: basic
  Type: basic

  Description: A user in the Deployer security role.

Back to Top

Response

200 Response

Back to Top