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
