You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Shadar <sh...@gmail.com> on 2009/06/02 15:42:25 UTC
Re: jmeter-2.3.3 Prepared Select Statement fails with "This
statement has been closed."
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?
-- Shaul
On 02/06/2009, Shadar <sh...@gmail.com> 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: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: jmeter-2.3.3 Prepared Select Statement fails with "This statement
has been closed."
Posted by Kenneth Cox <ke...@gmail.com>.
What I did to get a log file: right-click on Thread Group and choose Add
>> Listener >> View Results in Table, then type a filename and rerun.
Ken
On Tue, 02 Jun 2009 09:42:25 -0400, Shadar <sh...@gmail.com> 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?
> -- Shaul
>
>
> On 02/06/2009, Shadar <sh...@gmail.com> 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
>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: jmeter-2.3.3 Prepared Select Statement fails with "This statement
has been closed."
Posted by sebb <se...@gmail.com>.
On 02/06/2009, Shadar <sh...@gmail.com> 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 <sh...@gmail.com> 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: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org