Bug 51893

Summary: JMX notification/Exception for empty/exhausted connection pool
Product: Tomcat Modules Reporter: hay_dave
Component: jdbc-poolAssignee: Tomcat Developers Mailing List <dev>
Status: RESOLVED FIXED    
Severity: normal CC: rob.moore+apache
Priority: P2    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   

Description hay_dave 2011-09-26 14:49:49 UTC 
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])
Comment 1 Filip Hanik 2012-03-20 16:44:30 UTC 
Fixed in r1302990