I've had a look at the JDBC code, and I cannot see any reason why the status should be set to failed if the sample succeeds.
Do you get the same result for other types of SQL requests? On 06/04/2008, heidiaspell <[EMAIL PROTECTED]> wrote: > > JDBC Request shows the following on the Sampler Result tab: > > Thread Name: Thread Group 1-1 > Sample Start: 2008-04-07 08:45:30 NZST > Load time: 0 > Latency: 0 > Size in bytes: 4 > Sample Count: 1 > Error Count: 1 > Response code: > Response message: > > Response headers: > [EMAIL PROTECTED] > > Note: I am being correctly returned Response Data from the query. > > > > sebb-2-2 wrote: > > > > What does the Sampler Result tab show for the Response Code and > > Response Message? > > > > > > On 06/04/2008, heidiaspell <[EMAIL PROTECTED]> wrote: > >> > >> As previously mentioned, there are no errors detailed in jmeter.log. > >> > >> 2008/04/07 08:44:56 INFO - jmeter.engine.StandardJMeterEngine: Running > >> the > >> test! > >> 2008/04/07 08:44:56 INFO - jmeter.gui.util.JMeterMenuBar: > >> setRunning(true,*local*) > >> 2008/04/07 08:44:56 INFO - jmeter.engine.StandardJMeterEngine: Starting > >> 1 > >> threads for group Thread Group. Ramp up = 1. > >> 2008/04/07 08:44:56 INFO - jmeter.engine.StandardJMeterEngine: Test > >> will > >> stop on error > >> 2008/04/07 08:44:56 INFO - jmeter.threads.JMeterThread: Thread Thread > >> Group > >> 1-1 started > >> 2008/04/07 08:45:30 INFO - jmeter.threads.JMeterThread: Stop Test > >> detected > >> by thread Thread Group 1-1 > >> 2008/04/07 08:45:30 INFO - jmeter.threads.JMeterThread: Stopping Thread > >> Group 1-1 > >> 2008/04/07 08:45:30 INFO - jmeter.threads.JMeterThread: Thread Thread > >> Group > >> 1-1 is done > >> 2008/04/07 08:45:30 INFO - jmeter.engine.StandardJMeterEngine: Ending > >> thread Thread Group 1-1 > >> 2008/04/07 08:45:30 INFO - jmeter.engine.StandardJMeterEngine: Stopping > >> test > >> 2008/04/07 08:45:30 INFO - jmeter.engine.StandardJMeterEngine: > >> Notifying > >> test listeners of end of test > >> 2008/04/07 08:45:30 INFO - jmeter.gui.util.JMeterMenuBar: > >> setRunning(false,*local*) > >> 2008/04/07 08:45:30 INFO - jmeter.engine.StandardJMeterEngine: Test has > >> ended > >> > >> > >> > >> sebb-2-2 wrote: > >> > > >> > Check jmeter.log for any errors. > >> > > >> > On 06/04/2008, heidiaspell <[EMAIL PROTECTED]> wrote: > >> >> > >> >> I'm using JMeter 2.3.1 > >> >> > >> >> I am not using an Assertion. Here is the structure of my test: > >> >> > >> >> - Loop Controller > >> >> -- Simple Controller > >> >> --- JDBC Request > >> >> ---- Regular Expression Extractor > >> >> > >> >> My JDBC Request has a Query Type of "Select Statement". > >> >> > >> >> > >> >> > >> >> > >> >> sebb-2-2 wrote: > >> >> > > >> >> > Are you using an Assertion? That can set the status to failure. > >> >> > > >> >> > Which version of JMeter? > >> >> > > >> >> > On 03/04/2008, heidiaspell <[EMAIL PROTECTED]> wrote: > >> >> >> > >> >> >> I'm using a JDBC Request to perform a simple Select statement on > >> a > >> >> SQL > >> >> >> Server > >> >> >> db. > >> >> >> > >> >> >> The Results Tree Response Data tab shows that the results were > >> >> returned > >> >> >> correctly, but the Sampler Result tab still shows Error Count: > >> 1. > >> >> >> > >> >> >> The Summary Report shows 100% failure for my JDBC Request. > >> >> >> > >> >> >> There are no errors in the jmeter.log. > >> >> >> > >> >> >> Anyone have any ideas? I'm keen to get my tests running with 0% > >> >> errors. > >> >> >> > >> >> >> -- > >> >> >> View this message in context: > >> >> >> > >> >> > >> > http://www.nabble.com/JDBC-Request-returns-results-but-still-shows-Error-Count%3A-1-tp16473795p16473795.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] > >> >> > > >> >> > > >> >> > > >> >> > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> > http://www.nabble.com/JDBC-Request-returns-results-but-still-shows-Error-Count%3A-1-tp16473795p16528663.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] > >> > > >> > > >> > > >> > >> -- > >> > >> View this message in context: > >> > http://www.nabble.com/JDBC-Request-returns-results-but-still-shows-Error-Count%3A-1-tp16473795p16529594.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] > > > > > > > > -- > > View this message in context: > http://www.nabble.com/JDBC-Request-returns-results-but-still-shows-Error-Count%3A-1-tp16473795p16529796.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]
