T-42

What I wanted to achieve was just to speed up some manual testing during which I did the same database accesses again and again (in a Spring Boot / Batch application). Since the database in question is accessed read-only, I don't need any cleanup to repeat the test. For the moment, I think I'll get the task done faster if I just live with the performance of the real database. But I will probably come back to dbdatestdriver some day. Thanks again. Regards, T-42

Hi mbcon, with the connection pool size 1, our application hung. jstack showed threads in org.hibernate.query.Query.list with the same "parking to wait for <0x0000000642450680>", but no other line with that number (i.e. no owner of that monitor). After 25 minutes with no changes in jstack output, I killed the process. Anyway, this looks like a bug on our side, not in DbdaTestDriver. "pool-2-thread-13" #366 prio=5 os_prio=0 tid=0x0000000029ec1800 nid=0x7ec waiting on condition [0x0000000044e9d000]...

Hi, thank you very much for the bug fix. I can confirm that that issue is fixed also on Informix. Unfortunately, I run into another issue which I could not isolate into a test: java.lang.RuntimeException: Unexpected invocation exception: getDate : java.lang.NullPointerException : null at conpar.dbda.test.driver.record.BaseRecordHandler.invoke(BaseRecordHandler.java:75) at com.sun.proxy.$Proxy229.getDate(Unknown Source) at org.apache.commons.dbcp2.DelegatingResultSet.getDate(DelegatingResultSet.java:309)...

Hi, Connection.getWarnings() throws an exception: java.lang.RuntimeException: Unexpected invocation exception: getWarnings : java.lang.NullPointerException : null at conpar.dbda.test.driver.record.BaseRecordHandler.invoke(BaseRecordHandler.java:74) I encountered that on Informix an reproduced on HSQLDB. Please see attached test case (with Eclipse project setup). As you can see when switching to plain HSQLDB without DbdaTestDriver (i.e. using the commented DriverManager.getConnection statement instead),...