In the Administration Console, you can manually suspend individual
instances of a data source. When you suspend a data source, applications
can no longer get a database connection from the data source. For
connections that are already reserved by an application, behavior
depends on the type of suspension that you select:
- Suspend - which marks the data source as disabled and blocks any
new connection requests. If there are any reserved connections, the
operation will wait for InactiveTimeout seconds
if configured, otherwise the operation waits 60 seconds before
suspending all connections. If successful, the health state is set to
Suspended. All connections are preserved
exactly as they were before the data source was suspended. If you
Resume, clients that had reserved a connection
before the data source was suspended can continue exactly where they
left off.
- Force Suspend - which marks the data source as disabled. Any
transaction on any currently reserved connection is rolled back, and
all reserved connections are destroyed. Any subsequent attempts by
applications to use their reserved connections will fail. If
successful, the health state is set to
Suspended. At this time, the data source
attempts to replenish the connection pool by creating as many new
connections as had been destroyed. If you
Resume, clients must reserve new connections to
proceed.
To suspend a JDBC data source:
