Hello I hope to have some time available to do help with the development of JMeter in the coming weeks. I will be interested in improving the JDBC testing.
I don't see too much talk on JDBC testing in the mailing list. Does anybody know how much it's used for JDBC testing ? Does anybody know of features which are wanted for JDBC testing ? Below is some of the issues I hope to be able to contribute a bit to : (the order of the issues is random, and not prioritized) 1. Enhance the DbConnectionManager. First, there is a trivial bug, which causes a leak of a connection when the test starts. Secondly, and mainly, I find the whole connection pool code a bit too complex (but hey, maybe I'm misunderstanding things). I don't see the whole point of having the separate thread for resetting ConnectionObjects. Also, as the code is today, it leaks connections after the test has finished, because the separate thread resets connections (i.e. opens them) after the test has finished. I'll try to come up with a better design / code. If anybody would be interested in discussing the connection pooling, I'd be glad. 2. Implement a JDBC ConnectionSampler This sampler will only measure the time it takes to open a connection. So this sampler will not use any connection pool. It might also be possible to specify that you want to measure the time for opening and closing a connection. 3. Improve testing of JDBC insert statements. I'm thinking of having some GUI where the user can specify the data values he wants to insert, so that you for example can measure the time it takes to insert 100 rows of different values to one table. I'll also try to add support for testing "batch insert", so that we can measure if batch insert is faster or not. 4. Implementing a dummy JDBC driver. This is a bit beside JMeter, but in conjunction with the connection pooling, it would be useful to have a dummy JDBC driver, which would only contain debug code so that it would let us know if we are leaking connections, and so on. Does anybody know if such a dummy JDBC driver exists ? 5. Maybe add something for testing of stored procedures. I think I saw some posting about SP some time ago. Is there a need for work here. 6. Do you have any other issues with JDBC testing ? Feedback is welcomed. I cannot promise that I will have time to do this, but I sure hope so. Regards Alf Hogemark
