Hi all We did some debugging this morning. There is one thing in jOOQ that looks suspicious to us: For the first query, a DataSourceConnectionProvider is used. However, for the second and third (the one that fails because the connection is closed) query a DefaultConnectionProvider is used. The reason for this is in the AbstractStoreQuery -> execute() method:
DSLContext create = DSL.using(ctx.connection(), SQLDialect.SQLITE, ctx.configuration().settings()); -> triggers the creation of a DefaultConnectionProvider Shouldn't this be something like create(ctx.configuration()) instead? -> creates a configuration dependent connection provider I don't know if this is really related to our problem but anyway we have the feeling that this not correct :-) Thx & Regards, Michele Am Freitag, 3. Mai 2013 10:20:45 UTC+2 schrieb Joachim Durchholz: > > > I'm afraid, you'll might have to step through jOOQ > > code with the debugger to assess where and why the > > connection is really closed. > > I usually put a breakpoint on the close() function of the connection > object and inspect the stack trace to see who's calling the close(). > -- 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.
