[
https://issues.apache.org/jira/browse/DBCP-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901565#comment-13901565
]
Mark Thomas commented on DBCP-393:
----------------------------------
I suspect that the reason this feature hasn't been implemented to date is that
generally, failover requires some form of database replication and databases
that provide that tend to provide JDBC drivers that support failover as well.
I'm not against this feature - depending on what the patch look like - but I'm
not sufficiently motivated to write the patch myself. Without a patch, this is
eventually going to get resolved as WONTFIX.
> 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.5#6160)
