[jira] Updated: (DBCP-223) Auto-alert of connection pool critical events?

["Phil Steitz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DBCP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phil Steitz updated DBCP-223:
-----------------------------


There are no current or planned features for this kind of thing, though improved logging has been discussed.  Client code can keep track of exceptions and raise alerts as necessary and locally meaningful.

Leaving this open for now, but inclined to close as WONTFIX.  Specific suggestions for improvement to exceptions, logging or interfaces to get more information from the pool are welcome.

> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org