Hi everyone, We had encountered a problem with batch operations that would eat up our Connection Pool.
When a query is prepared for batch operation, it is, in a first step, almost executed by Jooq only to be stopped by a QueryCollectorSignal exception. The goal of this first step is to generated the SQL text (in a second phase, the sql is bound to all records for batch operation). However it seems that the connection opened in the first step is not correctly closed after the QueryCollectorSignal. As we use a Connection Pool, problems can be avoided by always "touching" the connection (open/close) after the transaction is started. The Connection Pool will then serve "proxies" to the subsequent 'openConnection' calls and it is no more critical if one of those is not correctly closed. (We have this workaround in place). Has someone else experienced the same problem? Thanks. Stan. -- 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/d/optout.
