Just to close this out, switching the mysql driver to com.mysql.jdbc.Driver
does appear to have fixed the problem. Thanks very much.
On 6 July 2012 16:26, Scott Ferguson <f...@caucho.com> wrote:
> On 07/06/2012 12:45 PM, Steven Cassidy wrote:
> > Hi, Thanks for the replies. I don't think there's a leak unless it
> > manifests itself only very occasionally. The stats now are Active 6,
> > Idle 133, Created 0.02% (757 / 3.3M), Failed 0, max-connections 256,
> > idle time 30000. The active count is not increasing.
> > The driver type in the pool definition is
> > com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource. The
> > connector/j version is mysql-connector-java-5.0.8-bin.jar. I'm
> > interested that you mention a known issue with mysql - could we be
> > seeing that possibly? Is there a fix, or somewhere I can learn about
> > the issue?
> The ConnectionPoolDataSource is at
> http://wiki4.caucho.com/Application_Server:_MySql_JDBC_Pooling and
> But if you don't have any threads waiting for a new connection in the
> driver (there should be at least one), it might be a different issue,
> and may be fixed in a later Resin version.
> -- Scott
resin-interest mailing list