Database Reference
In-Depth Information
you notice faulty transactions, server resources may still linger on. To prevent
losing server threads to these faulty XA resources, Oracle WebLogic Server JTA
has an internal resource health monitoring mechanism. A resource is considered
active if either there are no pending requests or the result from any of the XA
resource pending requests has not failed. If an XA resource is not active within
two minutes, the Oracle WebLogic Server transaction manager declares it dead
and any further requests to it are shunned.
The two minute interval can be configured by using the
MaxXACallMillis
JTA MBean attribute. It is currently not exposed through the Oracle WebLogic
Server Administration Console. You can, however, configure
MaxXACallMil-
lis
through Oracle Enterprise Manager Fusion Middleware Control. Follow
these steps to tune this property:
1.
Log in to Oracle Manager Fusion Middleware Control.
2.
Navigate to
WebLogic Domain
|
[Domain]
.
3.
Right-click on
AdminServer
and select
System MBean Browser
.
4.
Expand
Configuration MBeans
|
com.bea
|
JTA
and click on your domain.
5.
On the right-hand side, you will see additional information about the entire
configuration MBean for JTA. Override the default value for the
Read Write
(RW)
MBean
MaxXACallMillis
to a value of
240000
.
6.
Click on the
Apply
button to save this new setting.
Tuning data sources
Oracle SOA Suite 11g predominantly runs stateful processes. It utilizes a data-
base to store metadata and instance data during runtime. This data is stored in
what is known as the dehydration store. Oracle SOA Suite 11g leverages the de-
hydration store database to maintain long-running asynchronous processes and
their current state information while they wait for asynchronous callbacks. We
will cover management and monitoring of the dehydration store schema in de-
tail in
Chapter 8
,
Managing the Metadata Services Repository and Dehydration
Store
. The connection to this underlying dehydration store is maintained through
data source configurations on the application server. Hence, every application in
the SOA infrastructure constantly uses database connections to dehydrate and
rehydrate instance data. More often than not, database performance is impacted
