Re: [DBCP] Connection pool not behaving as I expect

2018-03-01 Thread Shawn Heisey
On 3/1/2018 8:48 PM, Matt Sicker wrote: Take a look inside commons-pool for the instrumentation (e.g., JMX). You can also track usage on borrow and other leaks. Also, Tomcat uses DBCP as it is. I know I can get those numbers from the object pool, but at the point where I needed them, I don't

Re: [DBCP] Connection pool not behaving as I expect

2018-03-01 Thread Matt Sicker
Take a look inside commons-pool for the instrumentation (e.g., JMX). You can also track usage on borrow and other leaks. Also, Tomcat uses DBCP as it is. On 1 March 2018 at 21:46, Shawn Heisey wrote: > On 3/1/2018 4:46 PM, Gary Gregory wrote: > >> I do not think this is a question I, or anyone

Re: [DBCP] Connection pool not behaving as I expect

2018-03-01 Thread Shawn Heisey
On 3/1/2018 4:46 PM, Gary Gregory wrote: I do not think this is a question I, or anyone here, can answer generically. I can read between that lines that you must feel frustrated and I certainly empathize with that. I think you might want to debug your application and come up with some parameters

Re: [DBCP] Connection pool not behaving as I expect

2018-03-01 Thread Phil Steitz
> On Mar 1, 2018, at 3:33 PM, Shawn Heisey wrote: > > We have been having some problems lately where our MySQL server hits the > max connection limit (600) and then everything breaks. When I look into > the problem, I find that our application servers have each made nearly a > hundred connecti

Re: [DBCP] Connection pool not behaving as I expect

2018-03-01 Thread Gary Gregory
On Thu, Mar 1, 2018 at 3:33 PM, Shawn Heisey wrote: > We have been having some problems lately where our MySQL server hits the > max connection limit (600) and then everything breaks. When I look into > the problem, I find that our application servers have each made nearly a > hundred connection

[DBCP] Connection pool not behaving as I expect

2018-03-01 Thread Shawn Heisey
We have been having some problems lately where our MySQL server hits the max connection limit (600) and then everything breaks.  When I look into the problem, I find that our application servers have each made nearly a hundred connections to the DB and haven't closed any of them for hours. I'm als