Database Reference
In-Depth Information
by insufficient resources on the application server side. The overall performance
of the infrastructure is immediately affected, if enough connections are not avail-
able in the Oracle WebLogic Server connection pool, and as such, tuning and
optimizing your backend database connections for Oracle SOA Suite 11g is es-
sential. Otherwise, you may end up seeing the following messages in your dia-
gnostic loggers:
Internal error: Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDisabledException: Pool is suspended, cannot allocate resources to applications
This problem can be encountered by increasing the connections or correctly di-
mensioning your data source connection pools to match the free sessions/pro-
cesses that your database can handle:
1.
Log in to Oracle Manager Fusion Middleware Control.
2.
Expand
WebLogic Domain
, right-click on your domain name, and click on
JDBC Data Sources
.
3.
From the list of all available data sources, click on
SOADatasource
(which
is the default transactional data source to connect to instance dehydration
store) and click on the
Connection Properties
tab.
4.
Override the default values for connection pool with the tuned value as
shown in the following table. Some of the settings are available by further
drilling down in the
Advanced
section.
Default
Value
Tuned
Value
Parameter Name
Remarks
oracle.net.CONNECT_TIMEOUT 10000 20000
You may receive many connection pool timeout errors such as
weblogic.common.resourcepool.ResourceDeadException
or
weblogic.common.ResourceException: Got minus
one from a read call
in scenarios where multiple instances
use multiple connection threads. When these errors occur, the
