tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51893] New: JMX notification/Exception for empty/exhausted connection pool
Date Mon, 26 Sep 2011 14:49:49 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51893

             Bug #: 51893
           Summary: JMX notification/Exception for empty/exhausted
                    connection pool
           Product: Tomcat Modules
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: jdbc-pool
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: hay_dave@yahoo.com
    Classification: Unclassified


Currently, if there is an error getting a connection from the pool, a generic
SQLException is thrown.  The only way to determine if the problem is a result
of the connection pool being exhausted is to catch the SQLException and parse
the message (i.e. look for "Pool empty" in ex.getMessage()).  Would like to see
the following:

1) A subclass of SQLException thrown in the case of an empty pool
2) A JMX notification sent in the case of an empty pool (e.g. [POOL EXHAUSTED])

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


Mime
View raw message