JMeter cannot log in - JMeter noob

Question

First of all, I don’t know how to really show you what exactly I work, and no one can actually get to the site, because it is a private network where the site lives. Here is a screenshot of JMeter:

I am just trying to log in to our site, but in the node presentation tree for "/ common / j_security_check" it does not work. The following is the information from the tab:

Sampler Result:

Thread Name: Thread Group 1-1 Sample Start: 2011-08-18 16:59:26 PDT Load time: 0 Latency: 0 Size in bytes: 795 Sample Count: 1 Error Count: 1 Response code: Non HTTP response code: java.lang.IllegalArgumentException Response message: Non HTTP response message: Entity enclosing requests cannot be redirected without user intervention Response headers: HTTPSampleResult fields: ContentType: DataEncoding: null 

Inquiry:

 POST https://DELETED BY ME (SORRY) POST data: [no cookies] Request Headers: 

Response data:

 ava.lang.IllegalArgumentException: Entity enclosing requests cannot be redirected without user intervention at org.apache.commons.httpclient.methods.EntityEnclosingMethod.setFollowRedirects(EntityEnclosingMethod.java:225) at org.apache.jmeter.protocol.http.sampler.HTTPSampler2.setupConnection(HTTPSampler2.java:623) at org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HTTPSampler2.java:890) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:965) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:951) at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:348) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:243) at java.lang.Thread.run(Unknown Source) 

Thanks for any help.

Answer 1

Try switching from Redirect automatically to Follow Redirects .

It seems like it is trying to redirect for authentication, which means that you probably need a cookie manager .

Answer 2

I would also look at the actual "real login" traffic on a network sniffer like Fiddler. Then I would look at the traffic that Jmeter generates by going through the same proxy sniffer (you can use network proxies). I had a similar problem on one client site, and it turned out that one of the requests went to the SSO server, which returned a domain cookie, which for some reason was not controlled by the standard cookie manager.