On 02/06/2009, Shadar <[email protected]> wrote: > > OK (the .jmx is the same). BTW, I see no errors in the log file, only in the > GUI (e.g. view results tree). Is there some setting I need to change to get > errors in the log file?
No, sampler errors are not reported in the jmeter log file. However you can use a sample result (JTL) file either by adding a Listener, e.g. http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Simple_Data_Writer Or by using command-line mode with the -l flag. See also http://jakarta.apache.org/jmeter/usermanual/listeners.html > -- Shaul > > > > On 02/06/2009, Shadar <[email protected]> wrote: > > > > Hi Kenneth, > > > > I had experienced the almost the exact same problem in the last two days. > > I > > suspect this is a JMeter bug and regression from 2.3.2, as the same test > > scenario worked in 2.3.2. I posted this to the dev forum > > > > > http://www.nabble.com/Bug-report-for-JMeter-2.3.3-(regression-from-2.3.2)%3A-JDBC-error---org.postgresql.util.PSQLException%3A-This-statement-has-been-closed-td23818467.html > > here . > > > > By the way, in my case even a simple select (e.g. "select 1") fails with > > this error, not only a prepared statement. Playing with the connection, > > including setting pool size to 0, did not help. > > I compared the JDBC code in 2.3.2 and 2.3.3, and could not see > anything relevant to this. > > If you are sure that this is a regression - i.e. the identical JMX > file works in 2.3.2 but does not work in 2.3.3 - then please file a > Bugzilla issue (see website for details) with full details, and attach > the following: > > JMX file > jmeter.log from 2.3.2 and 2.3.3 > > > -- > View this message in context: > http://www.nabble.com/jmeter-2.3.3-Prepared-Select-Statement-fails-with-%22This-statement-has-been-closed.%22-tp23821788p23832763.html > > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
