[DBCP-427] Consider SQLExceptions thrown by underlying connections or statements for fatal (disconnection) errors

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.4.1, 2.5.0
• Assignee: Unassigned
• Reporter: Vladimir Konkov
• Created: 04/Oct/14 11:08
• Updated: 01/Nov/18 19:09
• Resolved: 01/Nov/18 19:09

Description

Affected cases:
1. Ability to detect severed connection without need for validity check (it can be time demand).
2. Not all fatal errors detected with simple validation query or isValid() call. For example:
Broken XA connections of MS SQL Server and Oracle Database (and may be other) pass validation for both isValid() and simple validation query such as 'SELEC 1 FROM DUAL' but throw fatal errors on data and/or transaction manipulation calls. Such errors gone only after reconnect. In case of use DBCP for polling application has no chance to cleanup broken connection.

By providing infractructure for check thrown exceptions and mark PoolableConnection as poisoned we can cleanup pool on validation phase.

Issue Links

• is related to: DBCP-507 Change default for fail-fast connections from false to true