Thank you for the response guys. Yes, I do have assertions. And all the
users who were unable to login had those header response and all the users
who were succesfully able to login had the other response header. I ran th
test for 106 users to test the sso logins. I had the loop for two times.
The first time I ran the test all the users were not successfully able to
login. I tried running the test again and all the users were able to login
successfully. But I am getting this inconsistently.
The error on the logs (not jmeter logs)
ERROR[24-Jul-13 12:34:57] [http-0.0.0.0-9085-4]
[ChunkedInputStream.parseTrailerHeaders()]
- Error parsing trailer headers
org.apache.commons.httpclient.ProtocolException: Unable to parse header:
HTTP/1.1 200 OK
at
org.apache.commons.httpclient.HttpParser.parseHeaders(HttpParser.java:202)
at
org.apache.commons.httpclient.ChunkedInputStream.parseTrailerHeaders(ChunkedInputStream.java:322)
at
org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputStream.java:226)
On Jul 25, 2013 5:47 AM, "sebb" <[email protected]> wrote:
> On 25 July 2013 02:23, umesh prajapati <[email protected]> wrote:
> > Every time it has Successful request it has
> >
> > Response headers:
> > HTTP/1.1 200 OK
> > Server: Apache-Coyote/1.1
> > Pragma: no-cache
> > Expires: Thu, 01 Jan 1970 00:00:00 GMT
> > Cache-Control: no-cache
> > Cache-Control: no-store
> > Content-Type: text/html;charset=ISO-8859-1
> > Content-Language: en-US
> > Transfer-Encoding: chunked
> > Vary: Accept-Encoding
> > Date: Wed, 24 Jul 2013 23:23:11 GMT
> >
> > Every time it has Error
> >
> > Response headers:
> > HTTP/1.1 200 OK
> > Server: Apache-Coyote/1.1
> > Pragma: no-cache
> > Expires: Thu, 01 Jan 1970 00:00:00 GMT
> > Cache-Control: no-cache
> > Cache-Control: no-store
> > Content-Type: text/html;charset=ISO-8859-1
> > Content-Language: en-US
> > Content-Length: 2739
> > Vary: Accept-Encoding
> > Date: Wed, 24 Jul 2013 23:23:14 GMT
> >
> > So, I see the difference between successful and unsuccessful request is
> > Transfer-Encoding: chuncked (Successful)
> > Content-Length:2739 (unsuccessful)
> >
> > Anyone has any idea why I am getting this error.
>
> There is no error shown above.
> Both pages are successfully retrieved.
> It just happens that one page is returned using chunking, the other is not.
>
> Note that many servers don't send an HTTP error if an error such as
> invalid login occurs, they just display an error message in the
> returned page.
>
> To distinguish such errors from successful responses you will need to
> use a Response Assertion to check the actual page content.
>
> Make sure that whatever you choose to assert only appears in a
> successful response - and always occurs in successful responses.
> That way the unsuccessful response will be marked as failed.
>
> It's unlikely that the chunked/not chunked response headers will
> always correctly indicate success/failure.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>