I see that you have enabled leak-tracing & leak-reclaim. [You may have to set leak-tracing timeout for a larger value]
For more details on leak-tracing :
http://blogs.sun.com/kshitiz/entry/connection_leak_tracing
Looking at the stack trace there seems to be a connection leak by application. Suspect code is :
gov.shelbycountytn.ws.utilities.JdbcConnect.JdbcConn(JdbcConnect.java:35)
gov.shelbycountytn.ws.jss.BookingsOnIndictmentDao.getBookingsOnIndictment(BookingsOnIndictmentDao.java:18)
gov.shelbycountytn.ws.grandJury.CaseJacket.getBookingsOnIndictments(CaseJacket.java:124)
gov.shelbycountytn.ws.grandJury.CaseJacketDelegate.getBookingsOnIndictments(CaseJacketDelegate.java:56)
* Probably you will have to fix the code that is leaking the connection.
* When your pool is unsresponsive, do you see any error message (other than the one you have attached) ? If you dont see any exception, please post the jstack (thread dump) of appserver process.
[Message sent by forum member 'jr158900' (jr158900)]
http://forums.java.net/jive/thread.jspa?messageID=320894