Technical data

Additional Attributes for Managing Transactions
Administration Guide 15-5
You set these attributes directly in the config.xml file when the domain is inactive.
These attributes are not available in the Administration Console. The following
example shows an excerpt of a configuration file with these attributes:
...
<JTA
MaxUniqueNameStatistics="5"
TimeoutSeconds="300"
RecoveryThresholdMillis="150000"
MaxResourceUnavailableMillis="900000"
MaxResourceRequestOnServer="60"
MaxXACallMillis="180000"
/>
<JDBCConnectionPool
Name="XAPool"
Targets="myserver"
DriverName="weblogic.qa.tests.transaction.
testsupport.jdbc.XADataSource"
InitialCapacity="1"
MaxCapacity="10"
CapacityIncrement="2"
RefreshMinutes="5"
TestTableName="dual"
MaxResourceUnava
ilableMillis
weblogic.management.c
onfiguration.JTAMBean
The maximum duration (in milliseconds) that an XA
resource is marked as unhealthy. After this duration,
the XA resource is declared available again, even if
the resource is not explicitly re-registered with the
transaction manager. This setting applies to the entire
domain.
Default:
1800000
MaxResourceReque
stOnServer
weblogic.management.c
onfiguration.JTAMBean
Maximum number of concurrent requests to
resources allowed for each server in the domain.
Default:
50
Minimum: 10
Maximum: java.lang.Integer.MAX_VALUE
Table 15-2 XA Resource Health Monitoring Configuration Attributes
Attribute MBean Definition