Oracle 5.0 Reference Manual page 2078

tcpSndBuf
tcpTrafficClass
High Availability and Clustering.
Property Name
autoReconnect
autoReconnectForPools
failOverReadOnly
maxReconnects
reconnectAtTxEnd
retriesAllDown
initialTimeout
roundRobinLoadBalance
queriesBeforeRetryMaster
Connector/J (JDBC) Reference
If connecting using TCP/IP, should the driver set
SO_SND_BUF to the given value? The default
value of '0', means use the platform default value
for this property)
If connecting using TCP/IP, should
the driver set traffic class or type-of-
service fields ?See the documentation for
java.net.Socket.setTrafficClass() for more
information.
Definition
Should the driver try to re-establish stale and/
or dead connections? If enabled the driver will
throw an exception for a queries issued on a
stale or dead connection, which belong to the
current transaction, but will attempt reconnect
before the next query issued on the connection
in a new transaction. The use of this feature is
not recommended, because it has side effects
related to session state and data consistency
when applications don't handle SQLExceptions
properly, and is only designed to be used when
you are unable to configure your application to
handle SQLExceptions resulting from dead and
stale connections properly. Alternatively, as a
last option, investigate setting the MySQL server
variable "wait_timeout" to a high value, rather than
the default of 8 hours.
Use a reconnection strategy appropriate for
connection pools (defaults to 'false')
When failing over in autoReconnect mode, should
the connection be set to 'read-only'?
Maximum number of reconnects to attempt if
autoReconnect is true, default is '3'.
If autoReconnect is set to true, should the
driver attempt reconnections at the end of every
transaction?
When using loadbalancing, the number of times
the driver should cycle through available hosts,
attempting to connect. Between cycles, the driver
will pause for 250ms if no servers are available.
If autoReconnect is enabled, the initial time to wait
between re-connect attempts (in seconds, defaults
to '2').
When autoReconnect is enabled, and
failoverReadonly is false, should we pick hosts to
connect to on a round-robin basis?
Number of queries to issue before falling
back to master when failed over (when using
multi-host failover). Whichever condition
is met first, 'queriesBeforeRetryMaster' or
2058
0 5.0.7
0 5.0.7
Default Since
Value Version
false 1.1
false 3.1.3
true 3.0.12
3 1.1
false 3.0.10
120 5.1.6
2 1.1
false 3.1.2
50 3.0.2