mbcon

R4_1: FIX auto-record and multiple connections

Preparation of R4_0; JPA test bugfix

[ENH] SonarLint warnings removed, Auto-Record feature added

Removing Gradle wrapper

Info added.

Hi T-42, Thanks for sharing your situation and setup. I have fixed a bug in the local Logger class while playing around with JPA/Hibernate. The bug was related to TRACE logging. Maybe you ran into that issue. JPA works fine, at least for the (limited) testcase. Thanks again for providing me some input to improve the library. CU, mbcon

Hi T-42, no good news indeed. Of course I would have liked the fact that dbdatestdriver could have helped you whatever you are working on. I will spend some more time with a) Hibernate/JPA and b) the Taurus backend. If you want to invest some more time using the driver in the future, just keep in mind the basic idea and the restrictions that stem from that. Basically, the driver records all requests sent to the database serially, and therefore in replay mode, the database requests need to occur in...

Hi T-42, thanks for the feedback. Let's see what can be done regarding the issues you still have. I see that you are using Hibernate with a connection pool, and the Taurus backend. Since every connection needs to be proxied for the test driver to work, using a pool with a size > 1 is discouraged. Could you try to configure the pool to use only 1 connection (minimum size and maximum size)? Not sure if you can configure Hibernate to use no pool at all. Having done that, please run your tests again....