Ah, Wireshark. My friend calls it the "universal debugger". :) I will set the validation interval to 1 and keep an eye on the network to see what's going on. I may also install MySql locally so I can kill it easily to try and simulation connection timeouts. I won't really feel this is resolved until I can recreate the original issue.
Ultimately tho I'd still like to see some debug logging from the pool itself. Is there a simple way to turn it on? Thanks, Colin On Wed, Mar 21, 2012 at 11:20 AM, Filip Hanik Mailing Lists < devli...@hanik.com> wrote: > it will take a while to see the abandoned log. I'm not implying every > request hogs the connection, but that you could have ended up in a scenario > where that did happen. > otherwise, you would have not seen the problem for 2 hours and to go away > when the system was restarted, as it should have failed on validation. > > You can enable validation every single time by doing > > validationInterval="1" > > after that, if it was me, I'd start pulling in something like Wireshark to > see what is going on > > Filip > > ----- Original Message ----- > > From: "Colin Ingarfield" <colin...@gmail.com> > > To: "Tomcat Users List" <users@tomcat.apache.org> > > Sent: Wednesday, March 21, 2012 10:11:43 AM > > Subject: Re: how to enable debug logging for Tomcat jdbc pool (Tomcat > 6.0.32) > > > > I added the 3 abandoned settings but I don't see any indication in > > the > > tomcat log that connections are being abandoned. I also made the max > > pool > > size pretty small.. my application would have failed quickly if all > > the > > connections we're being incorrectly held up. > > > > Anything else I can try? Thanks again for your help. > > > > -- Colin > > > > On Wed, Mar 21, 2012 at 10:41 AM, Filip Hanik Mailing Lists < > > devli...@hanik.com> wrote: > > > > > Got it, thank you. > > > The other way this can happen is if the application checks out a > > > connection and then never returns it, and expects it to be used. > > > For this you will want to enable > > > > > > removeAbandonedTimeout="60" > > > removeAbandoned="true" > > > logAbandoned="true" > > > > > > this should tell you pretty quickly if you got a component that is > > > hogging > > > the connection. So test that first. Now if that is the case, there > > > is a way > > > to fix that: > > > > > > 1. remove the above settings > > > 2. compile and configure the interceptor described in: > > > https://issues.apache.org/bugzilla/show_bug.cgi?id=52024 > > > In this interceptor, when a failure occurs, it automatically > > > reconnects > > > and retries the operation. And that is the only way to get around > > > the > > > problem (assuming my assumption is correct) > > > > > > > > > Filip > > > ----- Original Message ----- > > > > From: "Colin Ingarfield" <colin...@gmail.com> > > > > To: users@tomcat.apache.org > > > > Sent: Wednesday, March 21, 2012 9:30:46 AM > > > > Subject: Re: how to enable debug logging for Tomcat jdbc pool > > > > (Tomcat > > > 6.0.32) > > > > > > > > My configuration: > > > > > > > > <Resource auth="Container" > > > > name="jdbc/cdb.mysql" > > > > defaultAutoCommit="false" > > > > driverClassName="com.mysql.jdbc.Driver" > > > > factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" > > > > url="jdbc:mysql://XXXXX.com/XXXX_dev?sessionVariables=TRANSACTION > > > > ISOLATION LEVEL READ COMMITTED" > > > > username="XXXXX" > > > > password="XXXXX" > > > > > > > > maxActive="100" > > > > maxIdle="100" > > > > minIdle="10" > > > > initialSize="10" > > > > maxWait="10000" > > > > testOnBorrow="true" > > > > type="javax.sql.DataSource" > > > > validationQuery="SELECT 1"/> > > > > > > > > > > > > I have testOnBorrow and validationQuery set as you suggest, so I > > > > do > > > > not > > > > think that is the issue. > > > > > > > > Thanks, > > > > Colin > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
