Thanks everyone.

I eventually went with BoneCP and it was fairly painless.  I was a little
puzzled that all of their examples involve grabbing a connection, and then
closing it.  Initially I thought that if you closed the connection it
wouldn't return to the pool, but I then realized that this is probably the
way you indicate that the connection can be returned to the pool.

It's also working quite nicely with Java 1.7's new try (Connection c =
pool.getConnection()) syntax.

@Andreas, thanks for the pointer to the built-in Connector/J pooling, I
think I'll stick with BoneCP as it seems simpler.

It's been a while since I've done this kind of J2EE stuff, so much of the
tooling is grossly overengineered, poorly documented, and they all manage
to make the simplest use-cases seriously over-complicated (I'm looking at
you Jersey).  jOOQ is a nice exception to that :-)

Ian.

On Tue, Mar 6, 2012 at 2:03 AM, Lukas Eder <[email protected]> wrote:

> Hello guys,
>
> @Ian: Good question. Yes, jOOQ explicitly avoids features like
> connection pooling, transaction handling, second-level caching etc.
> For all of these issues, there are already excellent tools out there
> that suit end users' needs better than what I could re-implement with
> jOOQ.
>
> @Vladislav: That's a nice Stack Overflow question with good research.
> I would probably have recommended c3p0, I wasn't aware that it has
> gotten somewhat outdated. Good to know. Do you have working examples
> with BoneCP and jOOQ? That might be something interesting for the jOOQ
> manual...
>
> @Andreas: Thanks for your input. You're probably right in this
> specific setup (MySQL / newbie). Pooling a couple of
> Oracle-connections in a J2EE system with 2000 - 10000 concurrent
> sessions is worth the trouble, if you don't want to kill the database.
> Tuning queries is another story :-)
>
> Cheers
> Lukas
>
> 2012/3/6 Andreas <[email protected]>:
> > 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.
>



-- 
[email protected]
Co-founder and CTO
OneSpot

Reply via email to