DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23110>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23110 JDBC Pool not completely cleaned up when in multiple thread groups ------- Additional Comments From [EMAIL PROTECTED] 2004-03-03 05:21 ------- ok... helps if you read the readme, eh? I used the build jakarta-jmeter-20040302. I created a sample test. - has a login defaults config element (connects to my local db2 v8 db user db2admin, password db2admin) - has a db connection pool defaults config element ( 5 connections/50 per conn) - has one thread group defined, 1 thread, 1 sec ramp up, loop count of 50 - has one single jdbc request as child of thread group: I try to blank out the db pool data entry fields, because I want it to use the defaults I created above, but after being blanked out, when I tab out of the field, each db pool field resets to "1" query string: select * from sysibm.systables - I then have a view results in table and a graph results listener Before I start the test, I do a db2 "list applications" command, which shows no apps connected to the database. I hit start, and the test runs successfully. I then do a "list applications" and I now see one connection still remains. I then start the test again, let it run, and once it completes successfully, I see I now have two connections to the database. So it looks like for each successful run, I get one additional database connection created that doesn't get cleaned up. I'm not certain as if this is due to my inability to clear out the settings for the jdbc pool data entry fields for the actual jdbc request object. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
