IBM Data Server Driver for JDBC and SQLJ client reroute support
The DB2 automatic client reroute feature allows client applications to recover from
a loss of communication with the server so that they can continue to work with
minimal interruption. JDBC and SQLJ client applications can take advantage of
that support.
Whenever a server crashes, each client that is connected to that server receives a
communication error, which terminates the connection and results in an application
error. When availability is important, you should have a redundant setup or
failover support. Failover is the ability of a server to take over operations when
another server fails. In either case, the IBM Data Server Driver for JDBC and SQLJ
client attempts to re-establish the connection to the original server or to a new
server. When the connection is reestablished, the application can continue with the
next transaction.
IBM Data Server Driver for JDBC and SQLJ client reroute support is available for
IBM Data Server Driver for JDBC and SQLJ type 4 connectivity to DB2 Database
for Linux, UNIX, and Windows, IBM Informix Dynamic Server, or DB2 for z/OS
servers. It works for connections that are obtained using the javax.sql.DataSource,
javax.sql.ConnectionPoolDataSource, javax.sql.XADataSource,or
java.sql.DriverManager interface.
Restriction: The IBM Data Server Driver for JDBC and SQLJ does not support
client reroute for an alternate DB2 Connect gateway, with the following exception:
If you set the alternate DB2 Connect gateway on the client side in one of the
following ways, the driver fails over to an alternate DB2 Connect gateway for the
initial connection only:
v Through a DB2ClientRerouteServerList instance
v By setting the clientRerouteAlternateServerName and
clientRerouteAlternatePortNumber properties
Restriction: The IBM Data Server Driver for JDBC and SQLJ does not support
client reroute when the user that is associated with a trusted connection is
switched without authentication. If the primary server is down after a program
executes a trusted user switch without authentication, client reroute to the
alternative server fails, and an SQLException is thrown.
Restriction: Client reroute support for connections that are made with the
DriverManager interface has the following restrictions:
v Alternate server information is shared between DriverManager connections only
if you create the connections with the same URL and properties.
v You cannot set the clientRerouteServerListJNDIName property or the
clientRerouteServerListJNDIContext properties for a DriverManager connection.
v Client reroute is not enabled for default connections (jdbc:default:connection).
Related reference
“Properties for the IBM Data Server Driver for JDBC and SQLJ” on page 201
“DB2ClientRerouteServerList class” on page 324
84 Application Programming Guide and Reference for Java
™
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To Next Page
Loading...
Need help?
General