Return-Path: X-Original-To: apmail-jmeter-user-archive@www.apache.org Delivered-To: apmail-jmeter-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DFA8710558 for ; Thu, 25 Jul 2013 19:42:34 +0000 (UTC) Received: (qmail 48162 invoked by uid 500); 25 Jul 2013 19:42:34 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 48079 invoked by uid 500); 25 Jul 2013 19:42:32 -0000 Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "JMeter Users List" Delivered-To: mailing list user@jmeter.apache.org Received: (qmail 48070 invoked by uid 99); 25 Jul 2013 19:42:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 19:42:32 +0000 X-ASF-Spam-Status: No, hits=0.3 required=5.0 tests=FREEMAIL_REPLY,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 74.125.82.179 as permitted sender) Received: from [74.125.82.179] (HELO mail-we0-f179.google.com) (74.125.82.179) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 19:42:25 +0000 Received: by mail-we0-f179.google.com with SMTP id t57so1050904wes.24 for ; Thu, 25 Jul 2013 12:42:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=noml9DyCo/q/I4+o/cz1VmVM6W4nNL3milVEpjfwuuE=; b=HRr7RDuHC02K62WjdeT7vFoHsFMp+zz5yjg0iJ3axHaYkGtyHU/eA1WoTg9BsZV0MX 0HBO34xTjCY9yfntJN7PSdUIKQLZ/i7HXyxisYUdxmTpwcY9nLaBRzuwIkSTk4R4KQCf 4ueehiyXmmV7TCZJMa/6daCMl44rLoFdoL/rysZSiKh8axT9ULGHGHTxoRO8U8Y+LNLW YyzjcIYSlNxEWkXoq8bhdHX6pZwkykJOVl4jCvbHI8k/q5pEmZW8TITlJAd8ke96C36J ovQgwbBrHXi0DgJ2drmtRW4DrS3TeEDIItgi9O2JB5MleJCgakPpHdKTXeJoc/YgOIhn NsEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=noml9DyCo/q/I4+o/cz1VmVM6W4nNL3milVEpjfwuuE=; b=TINvwJXeNOZFNrc8aEzw4fYajSsQTCYE5Foj6rIcinQhlrbZndqrHJGIZbk/wGo8HE NdOPMtApNXxPY4yn8KTUikZmENkGN90qhU8AvhRKEb2DKzouPkF/WkbiTAeEGdQ94aiK VfMTLI1gnTLWu8Em34iIc/JnWIsBv11A1b3TC7fOYKw/q4uyKpXlb+f8iY7EsIm9plDR SjJLuEq8nVu3WqlKQycUL5LwxDovVHOinTr7UDbQbInxYLSj6OpszPn4VvXhAoovpH2r 1yG+8oPSJJRhXaiiIicnbghkEUxu+aeNfqcxq05LeB85x2NDshCn+6+ATOyKgcfMUau+ acJQ== MIME-Version: 1.0 X-Received: by 10.180.24.197 with SMTP id w5mr3240609wif.25.1374781325042; Thu, 25 Jul 2013 12:42:05 -0700 (PDT) Received: by 10.194.152.103 with HTTP; Thu, 25 Jul 2013 12:42:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Jul 2013 20:42:04 +0100 Message-ID: Subject: Re: Error running the Test From: sebb To: JMeter Users List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 25 July 2013 17:32, umesh prajapati wrote: > No difference on the request tab...I will go ahead and try changing the > jmeter property and give it a try If the requests are identical, then it is starting to look like a load-related issue - possibly a threading issue - at the servr. How many threads are you running? > > On Thu, Jul 25, 2013 at 9:25 AM, sebb wrote: > >> On 25 July 2013 17:02, umesh prajapati wrote: >> > jmeter logs: >> > 2013/07/25 08:59:17 INFO - >> > org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl$4: I/O exception >> > (java.net.SocketException) caught when processing request: Connection >> reset >> > 2013/07/25 08:59:17 INFO - >> > org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl$4: Retrying request >> > 2013/07/25 08:59:20 INFO - >> > org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl$4: I/O exception >> > (java.net.SocketException) caught when processing request: Connection >> reset >> > 2013/07/25 08:59:20 INFO - >> > org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl$4: Retrying request >> >> Try setting the property >> >> httpclient4.retrycount=0 >> >> in jmeter.properties >> >> (will be the default for JMeter 2.10) >> >> This will report the error on the first sample, which is generally >> what you want for performance testing. >> Automatic retries can add unexpected traffic. >> >> > >> > On Thu, Jul 25, 2013 at 8:47 AM, umesh prajapati > >wrote: >> > >> >> I am looking at the view result tree (sample result tab)...The users who >> >> were able to login has load time (1000-3000) but the users who were not >> >> able to login has load time (60467-303469) >> >> >> >> >> >> On Thu, Jul 25, 2013 at 8:43 AM, umesh prajapati > >wrote: >> >> >> >>> I ran the test again using the http client 4 and I also checked marked >> >>> the browser compatible header but is still having the same issue >> (login >> >>> failures for some users) >> >>> >> >>> >> >>> On Thu, Jul 25, 2013 at 8:32 AM, umesh prajapati > >wrote: >> >>> >> >>>> I will let you know the result after I run the test using httpclient4 >> >>>> >> >>>> >> >>>> On Thu, Jul 25, 2013 at 8:31 AM, umesh prajapati < >> praumesh86@gmail.com>wrote: >> >>>> >> >>>>> I just ran the test again and at the beginning of the jmeter log >> before >> >>>>> the test started I saw these but not really sure if this is causing >> not to >> >>>>> login successful for some users >> >>>>> >> >>>>> 2013/07/25 08:11:00 INFO - >> >>>>> jmeter.protocol.http.sampler.HTTPSamplerBase: Cannot find .className >> >>>>> property for htmlParser, using default >> >>>>> >> >>>>> 2013/07/25 08:14:20 INFO - jmeter.util.SSLManager: KeyStore created >> OK >> >>>>> 2013/07/25 08:14:20 WARN - jmeter.util.SSLManager: Keystore file not >> >>>>> found, loading empty keystore >> >>>>> >> >>>>> >> >>>>> >> >>>>> On Thu, Jul 25, 2013 at 8:28 AM, sebb wrote: >> >>>>> >> >>>>>> On 25 July 2013 16:12, umesh prajapati >> wrote: >> >>>>>> > On my Http Request Currently I have these properties >> >>>>>> > >> >>>>>> > Implementation: Java >> >>>>>> >> >>>>>> Try using HttpClient 4 instead; >> >>>>>> >> >>>>>> The Java implementation is not ideal for testing. >> >>>>>> >> >>>>>> > Protocol: https >> >>>>>> > Method: Get >> >>>>>> > >> >>>>>> > >> >>>>>> > On Thu, Jul 25, 2013 at 8:10 AM, umesh prajapati < >> >>>>>> praumesh86@gmail.com>wrote: >> >>>>>> > >> >>>>>> >> server logs >> >>>>>> >> >> >>>>>> >> I am using jmeter version 2.9 >> >>>>>> >> >> >>>>>> >> Can you try using a different HTTP implementation (i.e. not >> Commons >> >>>>>> >> HttpClient)? >> >>>>>> >> do you mean to try different sampler request? >> >>>>>> >> >> >>>>>> >> >> >>>>>> >> >> >>>>>> >> On Thu, Jul 25, 2013 at 7:44 AM, sebb wrote: >> >>>>>> >> >> >>>>>> >>> On 25 July 2013 14:41, umesh prajapati >> >>>>>> wrote: >> >>>>>> >>> > 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) >> >>>>>> >>> >> >>>>>> >>> Which logs are they? >> >>>>>> >>> >> >>>>>> >>> > 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) >> >>>>>> >>> >> >>>>>> >>> >> >>>>>> >>> That looks like there might be an issue with the server sending >> bad >> >>>>>> >>> data or the HttpClient parsing code not recognising the >> response. >> >>>>>> >>> >> >>>>>> >>> Which version of JMeter are you using? >> >>>>>> >>> Can you try using a different HTTP implementation (i.e. not >> Commons >> >>>>>> >>> HttpClient)? >> >>>>>> >>> >> >>>>>> >>> >> >>>>>> >> --------------------------------------------------------------------- >> >>>>>> >>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org >> >>>>>> >>> For additional commands, e-mail: user-help@jmeter.apache.org >> >>>>>> >>> >> >>>>>> >>> >> >>>>>> >> >> >>>>>> >> >>>>>> >> --------------------------------------------------------------------- >> >>>>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org >> >>>>>> For additional commands, e-mail: user-help@jmeter.apache.org >> >>>>>> >> >>>>>> >> >>>>> >> >>>> >> >>> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org >> For additional commands, e-mail: user-help@jmeter.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org For additional commands, e-mail: user-help@jmeter.apache.org