http://albertech.net/2009/07/mysql-avoiding-the-mysqltoo-many-connections-error/ Tips, Tricks, and Reviews in Linux, Apache, MySQL, PHP Fri, 27 Aug 2010 19:12:02 +0000 hourly 1 http://wordpress.org/?v=3.0.1 http://albertech.net/2009/07/mysql-avoiding-the-mysqltoo-many-connections-error/comment-page-1/#comment-297 admin Thu, 03 Sep 2009 23:50:21 +0000 http://albertech.net/?p=208#comment-297 Thanks for the feedback on the tomcat connection to mySQL. Whats your max_connections setting in mySQL? Connection pooling uses tons of connections. Thanks for the feedback on the tomcat connection to mySQL. Whats your max_connections setting in mySQL? Connection pooling uses tons of connections.

]]> http://albertech.net/2009/07/mysql-avoiding-the-mysqltoo-many-connections-error/comment-page-1/#comment-296 jamescway Mon, 31 Aug 2009 22:09:48 +0000 http://albertech.net/?p=208#comment-296 following up...seems like tomcat doesn't like the 120sec wait_timeout, because it throws a broken pipe exception. Seems like it wants a more persistent connection, and I saw some people mention they put wait_timeout's of 9999999999 etc. Another solution was to put a validationQuery="/* ping */" in the resource of your server.xml file. That seemed to fix it for me. I still don't quite understand why it wants persistent, long lived connections. It would make sense to me for tomcat to automatically check to see if the connection was open before throwing exceptions. following up…seems like tomcat doesn’t like the 120sec wait_timeout, because it throws a broken pipe exception. Seems like it wants a more persistent connection, and I saw some people mention they put wait_timeout’s of 9999999999 etc. Another solution was to put a validationQuery=”/* ping */” in the resource of your server.xml file. That seemed to fix it for me. I still don’t quite understand why it wants persistent, long lived connections. It would make sense to me for tomcat to automatically check to see if the connection was open before throwing exceptions.

]]> http://albertech.net/2009/07/mysql-avoiding-the-mysqltoo-many-connections-error/comment-page-1/#comment-295 jamescway Mon, 31 Aug 2009 20:57:16 +0000 http://albertech.net/?p=208#comment-295 I didn't set my wait_timeout (in my.cnf) and it defaulted to 8hrs 28800 sec. Found out from select @@global.wait_timeout; So if my connections get used up within the 8 hrs, then when someone else connects then I won't have any connections to assign and the user will see server error. I will try to tune to 120sec and let you know how it goes. I didn’t set my wait_timeout (in my.cnf) and it defaulted to 8hrs 28800 sec. Found out from select @@global.wait_timeout;
So if my connections get used up within the 8 hrs, then when someone else connects then I won’t have any connections to assign and the user will see server error. I will try to tune to 120sec and let you know how it goes.

]]>