[
https://issues.apache.org/jira/browse/DBCP-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673665#comment-13673665
]
Ricardo Espirito Santo commented on DBCP-393:
---------------------------------------------
Hey Campbell,
What would the maxRetry be used for? If we'd be counting the number of failed
connection attempts it would need a cleaver mechanism of parsing failed
connection responses otherwise we could be retrying on impossible to recover
scenarios such as wrong password invalid username... etc...
DriverManagerConnectionFactory seems like a very straight forward
implementation and I wonder why none of this logic was ever included.
Can someone else please comment on this?
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
