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 261F6CDFC for ; Thu, 25 Jul 2013 16:56:37 +0000 (UTC) Received: (qmail 84542 invoked by uid 500); 25 Jul 2013 16:56:36 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 84476 invoked by uid 500); 25 Jul 2013 16:56:36 -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 84378 invoked by uid 99); 25 Jul 2013 16:56:35 -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 16:56:35 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of praumesh86@gmail.com designates 74.125.82.49 as permitted sender) Received: from [74.125.82.49] (HELO mail-wg0-f49.google.com) (74.125.82.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 16:56:28 +0000 Received: by mail-wg0-f49.google.com with SMTP id y10so1215228wgg.28 for ; Thu, 25 Jul 2013 09:56:07 -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=3MHNOqQwKu4aErlJI5r4ML+jmevzUIFbezhTxaKl+fo=; b=EG//3MqIZzcBvOILC7rCI+jgttWZDxsPhsbTWnVcORGZeITrb0LtnDgl7QeEr3/8km ToNmNbfIR5Ym5X84lDoviw1ITa/vb3OFfZPllqG3CV1Dl1VowaMwx2EprLA9TZbffgLw m/6Q+g+4YWVgDlKI4f3+erY56zmOzbN6iGfMdRMtDhCqgXflvxusuugKpLmENxnufq9d oPOBDN1cCi1Hg21Zx2LjM38ljZ9KRBrW48cvs7MRkaBo5aLtixzwehId5ls7PfhGc2uh b2vnlpXFjBCAkHQUpDx+aW/aTNx/eC9rR1yHPKOD2kEaRhGCeoF51bRTFL552Nqc9Grg 6EJA== MIME-Version: 1.0 X-Received: by 10.194.133.106 with SMTP id pb10mr31212322wjb.62.1374771367808; Thu, 25 Jul 2013 09:56:07 -0700 (PDT) Received: by 10.194.164.70 with HTTP; Thu, 25 Jul 2013 09:56:07 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Jul 2013 09:56:07 -0700 Message-ID: Subject: Re: Error running the Test From: umesh prajapati To: JMeter Users List Content-Type: multipart/alternative; boundary=089e0115f11206980304e258e719 X-Virus-Checked: Checked by ClamAV on apache.org --089e0115f11206980304e258e719 Content-Type: text/plain; charset=ISO-8859-1 I have ran the test as you have mentioned changing the jmeter property file but is still giving me the same issue. I have looked in the jmeter log and this is what I see 2013/07/25 09:53:28 INFO - org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl$4: I/O exception (java.net.SocketException) caught when processing request: Connection reset 2013/07/25 09:53:28 INFO - org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl$4: Retrying request 2013/07/25 09:53:33 INFO - org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl$4: I/O exception (java.net.SocketException) caught when processing request: Connection reset 2013/07/25 09:53:33 INFO - org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl$4: Retrying request On Thu, Jul 25, 2013 at 9:32 AM, umesh prajapati wrote: > No difference on the request tab...I will go ahead and try changing the > jmeter property and give it a try > > > 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 < >> praumesh86@gmail.com>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 >> >> > --089e0115f11206980304e258e719--