|
Oracle Fusion Middleware Java API Reference for Oracle WebLogic Server 12c (12.1.3) Part Number E41849-02 |
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface JTAClusterMBean
This interface provides access to the JTA configuration attributes. The methods defined herein are applicable for JTA configuration at the clluster level.
Field Summary |
---|
Fields inherited from interface weblogic.management.configuration.JTAMBean |
---|
CLIENTCERTREQUIRED, SSLNOTREQUIRED, SSLREQUIRED |
Fields inherited from interface weblogic.management.configuration.ConfigurationMBean |
---|
DEFAULT_EMPTY_BYTE_ARRAY |
Method Summary | |
---|---|
int |
getAbandonTimeoutSeconds()
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. |
int |
getBeforeCompletionIterationLimit()
The maximum number of cycles that the transaction manager performs the beforeCompletion synchronization callback for this cluster. |
int |
getCheckpointIntervalSeconds()
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. |
int |
getCompletionTimeoutSeconds()
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. |
String[] |
getDeterminers()
Specifies a list of one or more transaction resources (determiners) separated by line breaks. |
boolean |
getForgetHeuristics()
Specifies whether the transaction manager automatically performs an XA Resource forget operation for heuristic
transaction completions. |
int |
getMaxResourceRequestsOnServer()
Maximum number of concurrent requests to resources allowed for each server. |
long |
getMaxResourceUnavailableMillis()
Maximum duration time, in milliseconds, that a resource is declared dead. |
int |
getMaxTransactions()
The maximum number of simultaneous in-progress transactions allowed on a server in this cluster. |
long |
getMaxTransactionsHealthIntervalMillis()
The interval for which the transaction map must be full for the JTA subsystem to declare its health as CRITICAL. |
int |
getMaxUniqueNameStatistics()
The maximum number of unique transaction names for which statistics are maintained. |
long |
getMaxXACallMillis()
Maximum allowed time duration, in milliseconds, for XA calls to resources. |
int |
getMigrationCheckpointIntervalSeconds()
The time interval, in seconds, that the checkpoint is done for the migrated transaction logs (TLOGs). |
String |
getParallelXADispatchPolicy()
The dispatch policy to use when performing XA operations in parallel. |
boolean |
getParallelXAEnabled()
Indicates that XA calls are executed in parallel if there are available threads. |
int |
getPurgeResourceFromCheckpointIntervalSeconds()
The interval that a particular resource must be accessed within for it to be included in the checkpoint record. |
long |
getRecoveryThresholdMillis()
The interval that recovery is attempted until the resource becomes available. |
String |
getSecurityInteropMode()
Specifies the security mode of the communication channel used for XA calls between servers that participate in a global transaction. |
long |
getSerializeEnlistmentsGCIntervalMillis()
The time interval, in milliseconds, at which internal objects used to serialize resource enlistment are cleaned up. |
int |
getTimeoutSeconds()
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. |
int |
getUnregisterResourceGracePeriod()
The amount of time, in seconds, a transaction manager waits for transactions involving the resource to complete before unregistering a resource. |
String |
getWSATTransportSecurityMode()
Specifies transport security mode required by WebService Transaction endpoints. |
boolean |
isClusterwideRecoveryEnabled()
Indicates that cluster-wide recovery is used for distributed transactions. |
boolean |
isTightlyCoupledTransactionsEnabled()
Indicates tight coupling of transaction branches that span different transaction manager systems. |
boolean |
isTLOGWriteWhenDeterminerExistsEnabled()
Indicates two-phase transaction recovery logs are written even if one or more determiners are configured. |
boolean |
isTwoPhaseEnabled()
Indicates that the two-phase commit protocol is used to coordinate transactions across two or more resource managers. |
boolean |
isWSATIssuedTokenEnabled()
Specifies whether to use issuedtoken to enable authentication between the WS-AT
coordinator and participant. |
Methods inherited from interface weblogic.management.configuration.ConfigurationMBean |
---|
freezeCurrentValue, getId, getInheritedProperties, getName, getNotes, isDynamicallyCreated, isInherited, isSet, restoreDefaultValue, setComments, setDefaultedMBean, setName, setNotes, setPersistenceEnabled, unSet |
Methods inherited from interface weblogic.management.WebLogicMBean |
---|
getMBeanInfo, getObjectName, getParent, getType, isCachingDisabled, isRegistered, setParent |
Methods inherited from interface javax.management.DynamicMBean |
---|
getAttribute, getAttributes, invoke, setAttribute, setAttributes |
Methods inherited from interface javax.management.MBeanRegistration |
---|
postDeregister, postRegister, preDeregister, preRegister |
Methods inherited from interface javax.management.NotificationBroadcaster |
---|
addNotificationListener, getNotificationInfo, removeNotificationListener |
Methods inherited from interface weblogic.descriptor.DescriptorBean |
---|
addPropertyChangeListener, createChildCopyIncludingObsolete, getParentBean, isEditable, removePropertyChangeListener |
Method Detail |
---|
int getTimeoutSeconds()
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.
getTimeoutSeconds
in interface JTAMBean
int getAbandonTimeoutSeconds()
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.
getAbandonTimeoutSeconds
in interface JTAMBean
int getCompletionTimeoutSeconds()
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.
transaction-timeout
value with a maximum value of 120 seconds. This
value provides backward compatibility for prior releases without this setting.abandon-timeout-seconds
,
the value of abandon-timeout-seconds
is used.
getCompletionTimeoutSeconds
in interface JTAMBean
boolean getForgetHeuristics()
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.
getForgetHeuristics
in interface JTAMBean
int getBeforeCompletionIterationLimit()
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.
getBeforeCompletionIterationLimit
in interface JTAMBean
int getMaxTransactions()
The maximum number of simultaneous in-progress transactions allowed on a server in this cluster.
getMaxTransactions
in interface JTAMBean
int getMaxUniqueNameStatistics()
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."
getMaxUniqueNameStatistics
in interface JTAMBean
int getMaxResourceRequestsOnServer()
Maximum number of concurrent requests to resources allowed for each server.
getMaxResourceRequestsOnServer
in interface JTAMBean
long getMaxXACallMillis()
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.
getMaxXACallMillis
in interface JTAMBean
long getMaxResourceUnavailableMillis()
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.
getMaxResourceUnavailableMillis
in interface JTAMBean
long getRecoveryThresholdMillis()
The interval that recovery is attempted until the resource becomes available.
int getMigrationCheckpointIntervalSeconds()
The time interval, in seconds, that the checkpoint is done for the migrated transaction logs (TLOGs).
long getMaxTransactionsHealthIntervalMillis()
The interval for which the transaction map must be full for the JTA subsystem to declare its health as CRITICAL.
int getPurgeResourceFromCheckpointIntervalSeconds()
The interval that a particular resource must be accessed within for it to be included in the checkpoint record.
int getCheckpointIntervalSeconds()
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.
getCheckpointIntervalSeconds
in interface JTAMBean
long getSerializeEnlistmentsGCIntervalMillis()
The time interval, in milliseconds, at which internal objects used to serialize resource enlistment are cleaned up.
getSerializeEnlistmentsGCIntervalMillis
in interface JTAMBean
boolean getParallelXAEnabled()
Indicates that XA calls are executed in parallel if there are available threads.
String getParallelXADispatchPolicy()
The dispatch policy to use when performing XA operations in parallel.
int getUnregisterResourceGracePeriod()
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 0
, 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.
getUnregisterResourceGracePeriod
in interface JTAMBean
String getSecurityInteropMode()
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:
anonymous
otherwise.
Man-in-the-middle attacks are possible if the admin channel is not enabled.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.
getSecurityInteropMode
in interface JTAMBean
String getWSATTransportSecurityMode()
Specifies transport security mode required by WebService Transaction endpoints.
Transport Security options:
getWSATTransportSecurityMode
in interface JTAMBean
boolean isWSATIssuedTokenEnabled()
Specifies whether to use issuedtoken
to enable authentication between the WS-AT
coordinator and participant.
isWSATIssuedTokenEnabled
in interface JTAMBean
boolean isTwoPhaseEnabled()
Indicates that the two-phase commit protocol is used to coordinate transactions across two or more resource managers.
If not selected:
isTwoPhaseEnabled
in interface JTAMBean
boolean isClusterwideRecoveryEnabled()
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.
isClusterwideRecoveryEnabled
in interface JTAMBean
boolean isTightlyCoupledTransactionsEnabled()
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.
isTightlyCoupledTransactionsEnabled
in interface JTAMBean
String[] getDeterminers()
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.
getDeterminers
in interface JTAMBean
boolean isTLOGWriteWhenDeterminerExistsEnabled()
Indicates two-phase transaction recovery logs are written even if one or more determiners are configured.
isTLOGWriteWhenDeterminerExistsEnabled
in interface JTAMBean
|
Copyright 1996, 2014, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Oracle Fusion Middleware Java API Reference for Oracle WebLogic Server 12c (12.1.3) Part Number E41849-02 |
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |