[
https://issues.apache.org/jira/browse/DBCP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved DBCP-223.
------------------------------
Resolution: Fixed
I'm extremely reluctant to add specific functionality to DBCP for this. One
person's critical event will be another person's normal behaviour. The
configuration options required to differentiate between the two could easily
get out of hand.
My preferred approach is to expose the current state of the likely attributes
of interest (e.g. number of active connections currently borrowed from pool and
max connections available) and allow folks to use their monitoring solution of
choice to monitor those attributes and generate alerts as necessary.
As of DBCP 2, the pool attributes are all exposed via JMX. On this basis, I am
resolving this issue as fixed.
I am sure there is scope for improvement but any specific request to improve
what is currently available via JMX should be made in a new Jira issue.
> Auto-alert of connection pool critical events?
> ----------------------------------------------
>
> Key: DBCP-223
> URL: https://issues.apache.org/jira/browse/DBCP-223
> Project: Commons Dbcp
> Issue Type: New Feature
> Affects Versions: 1.2.2
> Environment: Windows, Unix
> Reporter: Bill Liu
> Fix For: 2.0
>
>
> Is there a way that the DBCP automatically alerts critical events such as db
> down or max # of connections reached too frequently? I was wondering if
> there's something written or this should be a nice feature for the DBCP. Our
> ops team really need to be alerted right away if the DBCP has some critical
> events.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
