Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 37585 invoked from network); 28 Aug 2006 03:30:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Aug 2006 03:30:30 -0000 Received: (qmail 44642 invoked by uid 500); 28 Aug 2006 03:30:28 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 44604 invoked by uid 500); 28 Aug 2006 03:30:28 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "JMeter Users List" Reply-To: "JMeter Users List" Delivered-To: mailing list jmeter-user@jakarta.apache.org Received: (qmail 44364 invoked by uid 99); 28 Aug 2006 03:30:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Aug 2006 20:30:27 -0700 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [209.10.209.56] (HELO mail.spikesource.com) (209.10.209.56) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Aug 2006 20:30:26 -0700 Received: from intra-web1.spikesource.com (softdnserr [::ffff:209.10.209.34]) by mail.spikesource.com with esmtp; Sun, 27 Aug 2006 20:30:05 -0700 id 00104C94.44F2633D.00002806 Received: from intra-web1.spikesource.com (localhost.localdomain [127.0.0.1]) by intra-web1.spikesource.com (8.13.1/8.13.1) with ESMTP id k7S3SnJD002759 for ; Sun, 27 Aug 2006 20:28:49 -0700 Received: (from oss@localhost) by intra-web1.spikesource.com (8.13.1/8.13.1/Submit) id k7S3SnpD002758; Sun, 27 Aug 2006 20:28:49 -0700 X-Authentication-Warning: intra-web1.spikesource.com: oss set sender to adhesiaseelan@spikesource.com using -f Received: from 125.16.130.66 (SquirrelMail authenticated user adhesiaseelan) by 209.10.209.38 with HTTP; Sun, 27 Aug 2006 20:28:49 -0700 (PDT) Message-ID: <62645.125.16.130.66.1156735729.squirrel@209.10.209.38> Date: Sun, 27 Aug 2006 20:28:49 -0700 (PDT) Subject: RE: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: problem with XML-RPC request using JMeter From: adhesiaseelan@spikesource.com To: "JMeter Users List" User-Agent: SquirrelMail/1.4.5 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_amazon-10246-1156735805-0001-2" X-Priority: 3 (Normal) Importance: Normal References: In-Reply-To: <9EFC04356BBC4745B67A41B106F4A47A01BCD3D0@TPN-EX01.PROJECT-NETWORK.COM > X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=_amazon-10246-1156735805-0001-2 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mime-Autoconverted: from 8bit to 7bit by courier 0.46 AJ, I am using the Web Server bundled by Apache XML-RPC library 2.0.1. The RPC methods are registered as handlers to this web server. The JMeter version I use is 2.2. Thanks, Arul -----Original Message----- From: Alex Turner [mailto:Alex.Turner@Project-Network.com] Sent: Monday, August 28, 2006 2:09 AM To: JMeter Users List Subject: RE: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: problem with XML-RPC request using JMeter Arul, What server are you using? AJ Alexander J Turner Ph.D. www.deployview.com www.nerds-central.blogspot.com www.project-network.com -----Original Message----- From: adhesiaseelan@spikesource.com [mailto:adhesiaseelan@spikesource.com] Sent: 27 August 2006 17:59 To: JMeter Users List Subject: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: problem with XML-RPC request using JMeter Thanks AJ. How do I turn off chunked encoding? I appreciate your help. Best regards, Arul -----Original Message----- From: Alex Turner [mailto:Alex.Turner@Project-Network.com] Sent: Sunday, August 27, 2006 2:19 AM To: JMeter Users List Subject: RE: TPN POSSIBLE SPAM:RE: problem with XML-RPC request using JMeter It is because your transfer encoding is chunked, that is the chunk length. Either you'll have to get JMeter to accept the chunked encoding (not sure why it is not automatically) or turn off chunked encoding. Technically speaking, the XML-RPC standard says that the message headers should have the message length, and XML-RPC does not say anything about chunking. So - I guess that it is reasonable that the sampler will not work with chunking. This is a shame - as I also (naughty - slap hands) send xml-rpc over http 1.1 chunked transfer. Cheers AJ Alexander J Turner Ph.D. www.deployview.com www.nerds-central.blogspot.com www.project-network.com -----Original Message----- From: adhesiaseelan@spikesource.com [mailto:adhesiaseelan@spikesource.com] Sent: 26 August 2006 20:23 To: JMeter Users List Subject: TPN POSSIBLE SPAM:RE: problem with XML-RPC request using JMeter Any body out there to help me? Why am I getting the garbage "16f" after the http header and before the xml request? Please clarify. Thanks, Arul -----Original Message----- From: Arulazi Dhesiaseelan [mailto:adhesiaseelan@spikesource.com] Sent: Friday, August 25, 2006 7:38 PM To: jmeter-user@jakarta.apache.org Subject: problem with XML-RPC request using JMeter Hello everybody, I am trying to load test a XML-RPC service using JMeter. I used the SOAP/XML-RPC Request sampler for sending the RPC requests. The sample request is shown below. myMethod 12 sdfd 213213 91 df 0 123 I get the following error in the server side: Fatal error parsing XML: org.xml.sax.SAXParseException: expected Element org.apache.xmlrpc.ParseFailed: org.xml.sax.SAXParseException: expected Element When I tried intercepting JMeter requests to my server using tcpmon, I see the following RPC request. -------------------------------------------------------------------------- -- --- POST / HTTP/1.1 Connection: close User-Agent: Jakarta Commons-HttpClient/3.0.1 Transfer-Encoding: chunked Content-Type: text/xml Host: 127.0.0.1:9999 16f myMethod 12 sdfd 213213 91 df 0 123 0 -------------------------------------------------------------------------- -- --- I could see some garbage (highlighted) before and after the request. If I remove this garbage in tcpmon and resend, the RPC call works fine. Why is this behavior? Am I missing something? Or JMeter is sending wrong requests. Please clarify. Thanks, Arul -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.6/427 - Release Date: 24/08/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.6/427 - Release Date: 24/08/2006 --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.6/427 - Release Date: 24/08/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.6/427 - Release Date: 24/08/2006 --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org --=_amazon-10246-1156735805-0001-2 Content-Type: text/plain; charset=us-ascii --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org --=_amazon-10246-1156735805-0001-2--