Bug report for JMeter [2009/05/31]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=NormalENH=Enhancement TRV=Trivial | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | |11536|Ass|Enh|2002-08-07|Graph Results's throughput calculation includes id| |15468|New|Enh|2002-12-18|Variable expansion in posted files in HTTPSampler | |15999|New|Enh|2003-01-12|Show Results Tree is too HTTP-centric | |16370|New|Enh|2003-01-23|HTTP Request log | |16886|New|Enh|2003-02-07|Recorded requests shouldn't duplicate info in HTTP| |17248|New|Enh|2003-02-20|Graph Improvements| |17252|Ass|Enh|2003-02-20|HTML Link Parser seems not work properly. | |21695|New|Enh|2003-07-17|Unix jmeter start script assumes it is on PATH, no| |22076|New|Enh|2003-08-01|global search and replace functionality | |22510|New|Maj|2003-08-18|SSL Manager does not handle multiple client certif| |24480|New|Enh|2003-11-06|There is no good way to set checkbox based items u| |25209|New|Min|2003-12-04|missed refresh of horizontal scrollbar when switch| |25430|New|Enh|2003-12-11|Recording Controller to populate HTTP Authorisatio| |27112|New|Enh|2004-02-20|User Parameters should use scrollbars | |27895|New|Enh|2004-03-24|badly formatted JDBC output (a regression w.r.t. 1| |28502|New|Enh|2004-04-20|HTTP Resource Cache | |29331|New|Enh|2004-06-01|how to load test java applet using JMeter | |29352|New|Enh|2004-06-03|Use external store to hold samples during distribu| |29603|New|Enh|2004-06-16|Custom component developers need own resource bund| |29708|New|Enh|2004-06-21|startup delay by JMeterThread initialization | |30563|New|Enh|2004-08-10|Thread Group should have a restart loop option on | |31666|New|Enh|2004-10-12|writing sampleresults to databases| |32494|New|Enh|2004-12-02|Enhancement - scheduler should be added to Test Pl| |33305|New|Enh|2005-01-31|Visual diff and merge functionality for JMeter scr| |33878|New|Enh|2005-03-07|Function caching as option| |33940|Opn|Nor|2005-03-09|Throughput value and Graph Results Graphing don'| |34321|New|Enh|2005-04-06|password encryption for HTTP Authorization Manager| |35059|New|Maj|2005-05-25|RuntimeController not working correctly | |35593|New|Enh|2005-07-03|Commons chain sampler | |35670|New|Enh|2005-07-09|Default parameters not displayed | |35915|New|Enh|2005-07-28|MonitorResults does not write results n CSV format| |36378|New|Enh|2005-08-26|[PATCH] A Thread Watcher Listener | |36694|New|Enh|2005-09-17|substitute a value in the input XML for webservice| |36721|New|Enh|2005-09-20|webMethods Sampling Protocol Extensions | |36726|New|Enh|2005-09-20|Activate ctrl F shortcut to search a text in the| |36931|New|Enh|2005-10-05|Printable Version of the Users Manual | |37073|New|Enh|2005-10-13|Lacking Poisson timer | |37124|New|Enh|2005-10-17|Need error feedback in the GUI, noticed this by ac| |37155|New|Enh|2005-10-19|Testplan: Stop... Continue| |37156|New|Enh|2005-10-19|Formatted view of Request in Results Tree | |37160|New|Enh|2005-10-19|Scalable distributed testing | |37525|New|Enh|2005-11-16|Web service sampler does not support multipart req| |38115|Inf|Nor|2006-01-04|decode from encoded string by IE | |38387|Ass|Enh|2006-01-25|allow to read(/send) mail messages encrypted/signe| |38832|New|Nor|2006-03-02|webservice request sampler adding xmlns:xmlns | |39219|New|Nor|2006-04-06|HTTP Server: You can't stop it after File-Open | |39509|New|Nor|2006-05-08|Once-only controller running twice| |39642|New|Enh|2006-05-23|Need a sampler forJMX mbean-servers. | |39812|New|Nor|2006-06-14|Problem with Webservice(SOAP)Request over https | |40011|New|Enh|2006-07-11|New Elements for use in JMeter| |40181|Ass|Enh|2006-08-03|Add a new Session Bean protocol extension |
Graham Little is out of the office.
I will be out of the office starting 01/06/2009 and will not return until 08/06/2009. Please email SCEE PD SCERT ACWCE for urgent ACWCE issues. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmas...@scee.net This footnote also confirms that this email message has been checked for all known viruses. Sony Computer Entertainment Europe Limited Registered Office: 10 Great Marlborough Street, London W1F 7LP, United Kingdom Registered in England: 3277793 ** - To unsubscribe, e-mail: jmeter-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-dev-h...@jakarta.apache.org
Bug report for JMeter 2.3.3 (regression from 2.3.2): JDBC error - org.postgresql.util.PSQLException: This statement has been closed
Hi, I am using JMeter to test against a postgresql 8.3 DB, using JDBC. I want to run random SQL queries (working with CSV till now -- that went well, and JMeter is great once you figure it out!). I just upgraded from JMeter 2.3.2 to 2.3.3 in order to get the new random variable config element. When I loaded in JMeter 2.3.3 the same .jms test plan I used before with JMeter 2.3.2 the first query went fine, but all the following ones give a JDBC error: org.postgresql.util.PSQLException: This statement has been closed. Note: after untarring 2.3.3 I placed the JDBC driver postgresql-8.3-603.jdbc4.jar in the lib folder, as I have done for 2.3.2. Also (though not relevant IMHO) I am using the StatAggVisualizer.jar, placed under lib/ext in 2.3.2 and 2.3.3. This seems to be related to JDBC connection. Has this changed in 2.3.3? I tried using only 1 thread and playing with the connection properties, but error persists. Please see if http://forums.sun.com/thread.jspa?threadID=782570 http://forums.sun.com/thread.jspa?threadID=782570 is related, in particular comment on the bottom. Also if I need to go back to 2.3.2, can you point me to explanation of how to use the __Random() function in a JDBC request SQL query, instead of the random variable config element? Thanks, -- Shaul -- View this message in context: http://www.nabble.com/Bug-report-for-JMeter-2.3.3-%28regression-from-2.3.2%29%3A-JDBC-error---org.postgresql.util.PSQLException%3A-This-statement-has-been-closed-tp23818467p23818467.html Sent from the JMeter - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: jmeter-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-dev-h...@jakarta.apache.org
Re: Bug report for JMeter 2.3.3 (regression from 2.3.2): JDBC error - org.postgresql.util.PSQLException: This statement has been closed
On 01/06/2009, Shadar shaul...@gmail.com wrote: Hi, I am using JMeter to test against a postgresql 8.3 DB, using JDBC. I want to run random SQL queries (working with CSV till now -- that went well, and JMeter is great once you figure it out!). I just upgraded from JMeter 2.3.2 to 2.3.3 in order to get the new random variable config element. When I loaded in JMeter 2.3.3 the same .jms test .jms ? plan I used before with JMeter 2.3.2 the first query went fine, but all the following ones give a JDBC error: org.postgresql.util.PSQLException: This statement has been closed. Check the JMeter log file as well. Note: after untarring 2.3.3 I placed the JDBC driver postgresql-8.3-603.jdbc4.jar in the lib folder, as I have done for 2.3.2. Also (though not relevant IMHO) I am using the StatAggVisualizer.jar, placed under lib/ext in 2.3.2 and 2.3.3. Try removing this just in case. This seems to be related to JDBC connection. Has this changed in 2.3.3? Yes - see the changes document - but the changes are unlikely to affect the behaviour in the way you are reporting. Are you using exactly the same JDBC driver? I tried using only 1 thread and playing with the connection properties, but error persists. Please see if http://forums.sun.com/thread.jspa?threadID=782570 http://forums.sun.com/thread.jspa?threadID=782570 is related, in particular comment on the bottom. No relevant as far as I can tell. Also if I need to go back to 2.3.2, can you point me to explanation of how to use the __Random() function in a JDBC request SQL query, instead of the random variable config element? See: http://jakarta.apache.org/jmeter/usermanual/functions.html#__Random Thanks, -- Shaul -- View this message in context: http://www.nabble.com/Bug-report-for-JMeter-2.3.3-%28regression-from-2.3.2%29%3A-JDBC-error---org.postgresql.util.PSQLException%3A-This-statement-has-been-closed-tp23818467p23818467.html Sent from the JMeter - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: jmeter-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-dev-h...@jakarta.apache.org - To unsubscribe, e-mail: jmeter-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-dev-h...@jakarta.apache.org
Re: Bug report for JMeter 2.3.3 (regression from 2.3.2): JDBC error - org.postgresql.util.PSQLException: This statement has been closed
On 01/06/2009, sebb seb...@gmail.com wrote: On 01/06/2009, Shadar shaul...@gmail.com wrote: Hi, I am using JMeter to test against a postgresql 8.3 DB, using JDBC. I want to run random SQL queries (working with CSV till now -- that went well, and JMeter is great once you figure it out!). I just upgraded from JMeter 2.3.2 to 2.3.3 in order to get the new random variable config element. When I loaded in JMeter 2.3.3 the same .jms test .jms ? plan I used before with JMeter 2.3.2 the first query went fine, but all the following ones give a JDBC error: org.postgresql.util.PSQLException: This statement has been closed. Check the JMeter log file as well. Note: after untarring 2.3.3 I placed the JDBC driver postgresql-8.3-603.jdbc4.jar in the lib folder, as I have done for 2.3.2. Also (though not relevant IMHO) I am using the StatAggVisualizer.jar, placed under lib/ext in 2.3.2 and 2.3.3. Try removing this just in case. This seems to be related to JDBC connection. Has this changed in 2.3.3? Yes - see the changes document - but the changes are unlikely to affect the behaviour in the way you are reporting. Are you using exactly the same JDBC driver? I tried using only 1 thread and playing with the connection properties, but error persists. Please see if http://forums.sun.com/thread.jspa?threadID=782570 http://forums.sun.com/thread.jspa?threadID=782570 is related, in particular comment on the bottom. No relevant as far as I can tell. Also if I need to go back to 2.3.2, can you point me to explanation of how to use the __Random() function in a JDBC request SQL query, instead of the random variable config element? See: http://jakarta.apache.org/jmeter/usermanual/functions.html#__Random Also, make sure you disable connection pooling, set Max Number of Connections = 0. Thanks, -- Shaul -- View this message in context: http://www.nabble.com/Bug-report-for-JMeter-2.3.3-%28regression-from-2.3.2%29%3A-JDBC-error---org.postgresql.util.PSQLException%3A-This-statement-has-been-closed-tp23818467p23818467.html Sent from the JMeter - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: jmeter-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-dev-h...@jakarta.apache.org - To unsubscribe, e-mail: jmeter-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-dev-h...@jakarta.apache.org
