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 ? + Sorry, meant .jmx 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. + No errors in log file. 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. + I did. No effect. 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 behavior in the way you are reporting. Are you using exactly the same JDBC driver? + Yes. If I remove the driver I get a missing driver error. It is enough to have a JDBC Connection config + JDBC request (e.g. select 1) to create this error, on iteration 2 and higher 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 + Yes, I read about that. What I meant is how di I use it in a select statement? Also is there a workaround in 2.3.2 to the nice functionality added in 2.3.3 of saving JDBC Request query results to variables (allows for continuation queries)? Thanks again, -- 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-tp23818467p23830470.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
... This is getting off-topic for the JMeter developers list; please post a new query to the JMeter user list. Sorry, but it does look like a bug to me hence I thought the dev list is appropriate... Where should I post this if suspect it might be a bug? -- 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-tp23818467p23831197.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
Thanks. This was good advice. I looked at the user group and saw an http://www.nabble.com/jmeter-2.3.3-Prepared-Select-Statement-fails-with-%22This-statement-has-been-closed.%22-td23821788.html identical post there . So I do suspect it's a bug. Can you point me to the exact Bugzilla URL? (sorry, never posted there). -- Shaul ... quote author=sebb-2-2 ... The JMeter user list. Say what you did, what happened, and what you expected to happen. If you are absolutely sure there is a bug you can raise it on Bugzilla, but it's best to check on the user list first. -- 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-tp23818467p23832045.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
Tried this earlier. Didn't help. Where exactly do I file a JMeter 2.3.3 bug on bugzilla, and what is the typical time for it to be looked at and fixed, if necessary? Thanks, -- Shaul sebb-2-2 wrote: Also, make sure you disable connection pooling, set Max Number of Connections = 0. On 02/06/2009, Shadar shaul...@gmail.com wrote: Thanks. This was good advice. I looked at the user group and saw an http://www.nabble.com/jmeter-2.3.3-Prepared-Select-Statement-fails-with-%22This-statement-has-been-closed.%22-td23821788.html identical post there . So I do suspect it's a bug. Can you point me to the exact Bugzilla URL? (sorry, never posted there). -- Shaul ... quote author=sebb-2-2 ... The JMeter user list. Say what you did, what happened, and what you expected to happen. If you are absolutely sure there is a bug you can raise it on Bugzilla, but it's best to check on the user list first. -- 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-tp23818467p23832045.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 -- 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-tp23818467p23832614.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
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
