[
https://issues.apache.org/jira/browse/DBCP-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796359#comment-13796359
]
Paulo Costa commented on DBCP-393:
----------------------------------
My solution for this was to implement a custom JDBC Driver.
When connecting to "foo://mygroup" the driver translates "mygroup" to all
possible servers and connects try connecting to all of them, returning
whichever succeeds first.
Yet, there were a number of special constraints in my environment that made the
JDBC Driver a good solution, it probably sounds like overkill for most uses.
> DBCP to support database connection failover
> --------------------------------------------
>
> Key: DBCP-393
> URL: https://issues.apache.org/jira/browse/DBCP-393
> Project: Commons Dbcp
> Issue Type: Improvement
> Affects Versions: 1.4
> Reporter: Campbell
> Priority: Critical
>
> Hello. Would it be possible for the DriverManagerConnectionFactory to accept
> a list or alternative database connection URL. With a possible maxRetry
> parameter, the suggestion is this improvement would allow for automatic fail
> over to a secondary database when a connection exception occurs.
> Let me know if this is a good candidate or if you have made thought of this
> already as it is standard behaviour in other managed datasources. Many thanks.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
