On 27/04/2009, Ed Young <[email protected]> wrote: > The snapshot jmeter version provides a bit more info about the Sampler > Result and indicates the ContentType is null. > > Note: I can invoke the servlet from a browser and the response is successful. > > I'm experimenting with an HTTP Header Manager to see if I can coerce > the header a bit. Still no Response Data.
The response shows that 34 bytes were received. Try adding a "Save Reponses to a file" element. > Sampler Result from jmeter version 2.3.2.20090427: > > > Thread Name: Thread Group 1-1 > > Sample Start: 2009-04-27 13:21:07 MDT > > Load time: 3 > Latency: 3 > Size in bytes: 34 So there was a response. > Sample Count: 1 > Error Count: 0 > Response code: 200 > Response message: OK > > Response headers: > HTTP/1.1 200 OK > > Transfer-Encoding: chunked > Server: Jetty(6.1.16) > > > HTTPSampleResult fields: > ContentType: > DataEncoding: ISO-8859-1 > > > > > On Mon, Apr 27, 2009 at 1:05 PM, Ed Young <[email protected]> wrote: > > I'm testing against a simple java servlet which as only one method. > > The content type returns null: > > System.out.println("content type" + request.getContentType()); > > > > returns: > > content type: null > > > > I've tried it with two jmeter versions: > > Version 2.3.2 r665936 > > > > I'll try the snapshot version I have too (2.3.2.20090427) and get the > > same result. > > > > Here's the log when I run it against the snapshot: > > 2009/04/27 13:03:11 INFO - jmeter.engine.StandardJMeterEngine: > > Running the test! > > 2009/04/27 13:03:11 INFO - jmeter.gui.util.JMeterMenuBar: > > setRunning(true,*local*) > > 2009/04/27 13:03:11 INFO - jmeter.engine.StandardJMeterEngine: > > Starting 1 threads for group Thread Group. Ramp up = 1. > > 2009/04/27 13:03:11 INFO - jmeter.engine.StandardJMeterEngine: > > Continue on error > > 2009/04/27 13:03:11 INFO - jmeter.threads.JMeterThread: Thread Thread > > Group 1-1 started > > 2009/04/27 13:03:11 INFO - jmeter.threads.JMeterThread: Thread Thread > > Group 1-1 is done > > 2009/04/27 13:03:11 INFO - jmeter.engine.StandardJMeterEngine: Ending > > thread Thread Group 1-1 > > 2009/04/27 13:03:11 INFO - jmeter.engine.StandardJMeterEngine: Stopping > test > > 2009/04/27 13:03:11 INFO - jmeter.engine.StandardJMeterEngine: > > Notifying test listeners of end of test > > 2009/04/27 13:03:11 INFO - jmeter.gui.util.JMeterMenuBar: > > setRunning(false,*local*) > > 2009/04/27 13:03:11 INFO - jmeter.engine.StandardJMeterEngine: Test has > ended > > > > > > > > On Mon, Apr 27, 2009 at 12:45 PM, sebb <[email protected]> wrote: > >> On 27/04/2009, Ed Young <[email protected]> wrote: > >>> This has got to be a simple problem/solution. I did do an archive > >>> search, but no luck. It's killing me... > >> > >> Which version of JMeter? > >> > >>> I'm sending the simplest of HTTP Requests and Jmeter indicates it got > >>> a response, I don't see it in the Viewe Results Tree "Response Data" > >>> tab. > >>> > >>> I can even see the response in Wireshark and it looks good. > >>> > >>> I put the HTTP Request as a child to the Thread Group and added a View > >>> Results Tree to it. > >>> > >>> Here's what the Sampler Result says: > >>> Thread Name: Thread Group 1-1 > >>> Sample Start: 2009-04-27 12:13:43 MDT > >>> Load time: 8 > >>> Latency: 8 > >>> Size in bytes: 34 > >>> Sample Count: 1 > >>> Error Count: 0 > >>> Response code: 200 > >>> Response message: OK > >>> > >>> Response headers: > >>> HTTP/1.1 200 OK > >>> Server: Apache-Coyote/1.1 > >>> Transfer-Encoding: chunked > >>> Date: Mon, 27 Apr 2009 18:13:29 GMT > >>> > >>> I'm tweaking all the View Results Tree parameters, but I can't see the > >>> response... > >> > >> Does this happen for all samples, or just this particular one? > >> Have you checked for errors in the JMeter log file? > >> > >> What is the Content-Type? > >> > >>> --------------------------------------------------------------------- > >>> 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] > >> > >> > > > > > > > > -- > > - Ed > > > > > > -- > - Ed > > --------------------------------------------------------------------- > 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]
