Hi Lukas thanks again for fast reply.
I've been working on self contained test and it seems problem was related to oracle driver ( connection pooling was not using universal connection pool ), after switching to ucp everything seems fine and performace tests all passed. Sorry for alerting you. Cheers Lucas W dniu wtorek, 9 lipca 2013 08:48:17 UTC+2 użytkownik Lukas Eder napisał: > > Hello, > > > 2013/7/8 <[email protected] <javascript:>> > >> Hi all, >> >> I'm evaluating possibility to use jooq in my project and i have problems >> while running performance tests. >> It seems that my connection pool is running out of connections. >> > > A couple of issues around that problem had been fixed recently. Are you > using the latest version of jOOQ? > > >> The problem occurs ( but I'm not sure it is real / the only reason ) >> while acquiring connection in AbstractRoutine.executeCallableStatement >> method. >> >> I've looked into this method and I am unable to find place where >> DefaultExecuteContext releases connection to connection provider. >> > > Connection lifecycle management is a bit distributed in jOOQ. To keep > things DRY, jOOQ wraps JDBC objects, which will guarantee that > ConnectionProvider.release() is called no matter how you access the jOOQ > API. There may be bugs, of course, so in order to reproduce your issue, > could you provide a simple, self-contained test case which will lead to the > problem you're having? > > Cheers > Lukas > > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
