On 21 Nov 2011, at 16:25, Martin O'Shea <[email protected]> wrote:
> Thanks Terence. > > Yes, I have been. Increasing the number of connections in MySQL, the > max_connections parameter, seems to have helped somewhat. If you are leaking connections it will just delay the problem, even make it worse. Connect VisualVM to Tomcat and monitor the connection pool, (assuming you have configured the pool as a Resource). If it keeps increasing in size, outgrowing the Connector threads, you have a leak. p > Is there an optimum number of connections that the 'equivalent' Tomcat > maxActive should have? > > -----Original Message----- > From: Terence M. Bandoian [mailto:[email protected]] > Sent: 21 Nov 2011 16 11 > To: Tomcat Users List > Subject: Re: Connection pooling issue with > MySQLNonTransientConnectionException and Java webapp > > > On 1:59 PM, Martin O'Shea wrote: >> Caused by: >> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: >> Data source rejected establishment of connection, message from >> server: "Too many connections" > > I'd check into this. > > -Terence Bandoian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
