Hi Ian, It seams to me that the MySQL Connector/J does support connection pooling: com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource Read http://dev.mysql.com/tech-resources/articles/connection_pooling_with_connectorj.html for almost helpful instructions.
Btw. Do you really need connection pooling? I've developed a fair amount of application which are using a database to store there data, and up to this point I never had performance problem with creating a new database connection. Even when in one of my web application I create >= 5 connection per request, the real bottleneck are the queries. In my opinion connection pooling only cloaks stuff and should only be used you are sure that you need it and you know what you are doing. I don't know what kind of application you are developing and what load you expect, but because you wrote "newbie" I couldn't resist to give you some advice. Andreas On Mar 5, 10:56 pm, Ian Clarke <[email protected]> wrote: > Or maybe not... turns out I was looking at the documentation for the .net > connector, so I need to reopen this question... > > Ian. > > > > > > > > On Monday, March 5, 2012 3:53:31 PM UTC-6, Ian Clarke wrote: > > > Ah, I just realized that Mysql's Java driver includes connection pooling > > by default, so I guess this question is probably moot. Sorry for bugging > > you :-) > > > Ian. > > > On Monday, March 5, 2012 3:47:31 PM UTC-6, Ian Clarke wrote: > > >> So, I realized that Jooq doesn't handle JDBC connection pooling, so I > >> need an external solution. Unfortunately it's not obvious which options > >> are best. Some appear hopelessly overcomplicated, others are unmaintained, > >> and others require additional large dependencies (such as Tomcat). I'm not > >> using any framework in my project other than Jersey and Grizzly to > >> implement a JSON-HTTP API. > > >> Can anyone recommend any connection pool options that work nicely with > >> Jooq? > > >> Thanks, > > >> Ian.
