Hi Lukas, Sorry, I haven't seen your old post.
Yes, i could be what you are explained. I also use Maven SQL plugin for create my DB, maybe it is this plugin that don't close the connection... For solve my problem, I have finally switch to H2 mem database, Regards, Alex Le vendredi 10 octobre 2014 13:28:57 UTC+2, Lukas Eder a écrit : > > Hi Alexandre, > > I've now had a similar experience with our integration tests and DBeaver > keeping an open "connection" to the Derby file when used in embedded mode. > It looks as though the DBeaver (also a Java application) process didn't > release the database file until I closed the program. So, closing the > connection doesn't seem to be enough... > > A quick search through Derby JIRA hasn't revealed any issues but maybe you > can confirm that this might be the problem? > > Cheers, > Lukas > > 2014-10-06 15:21 GMT+02:00 Lukas Eder <[email protected] <javascript:>>: > >> Hi Alexandre, >> >> Yes, that part I've understood. Yet, I don't succeed in reproducing it. >> Can you provide me with the relevant pom.xml and JUnit test, for instance? >> >> 2014-10-06 14:57 GMT+02:00 <[email protected] <javascript:>>: >> >> Hi Lukas, >>> >>> I have used a derby embedded DB (only one active connection) and in my >>> Junit unit test I create a new connection for testing jooq. >>> >>> When a package with maven, unit tests fail because there is already an >>> active connection. >>> >>> >>> >>> Le lundi 6 octobre 2014 10:50:32 UTC+2, Lukas Eder a écrit : >>>> >>>> I'm sorry, I may have been a bit too quick assuming that this is a bug. >>>> The GenerationTool closes the connection that it opens itself from the >>>> JDBC >>>> connection parameters provided with the code generation configuration. >>>> Could you maybe explain how this can be reproduced? >>>> >>>> 2014-09-30 9:11 GMT+02:00 <[email protected]>: >>>> >>>> Ok, thanks ! >>>>> >>>>> Le lundi 29 septembre 2014 18:20:36 UTC+2, Lukas Eder a écrit : >>>>>> >>>>>> You're right, that's a bug. I have registered an issue for this: >>>>>> https://github.com/jOOQ/jOOQ/issues/3655 >>>>>> >>>>>> One way for you to circumvent that bug is to patch the maven plugin >>>>>> and explicitly close the JDBC connection that is used in there. Another >>>>>> workaround would be to use dedicated profiles for generating source code >>>>>> in >>>>>> order to keep code generation isolated. >>>>>> >>>>>> Hope this helps, >>>>>> Lukas >>>>>> >>>>>> 2014-09-29 13:41 GMT+02:00 <[email protected]>: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I am using a derby embedded database for evaluating jooq. On this >>>>>>> database, I can only have one open connection. >>>>>>> >>>>>>> I have an issue with the jooq codegen maven plugin, it seems that >>>>>>> the plugin doesn't close the connection before starting unit test. >>>>>>> So, when maven run my units test, it throw an exception that a >>>>>>> connection is already open. >>>>>>> >>>>>>> Do you know why ? >>>>>>> >>>>>>> Thanks for your help. >>>>>>> >>>>>>> -- >>>>>>> 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. >>>>>>> >>>>>> >>>>>> -- >>>>> 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. >>>>> >>>> >>>> -- >>> 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] <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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.
