Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 40504 invoked from network); 28 Aug 2006 09:29:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Aug 2006 09:29:34 -0000 Received: (qmail 38902 invoked by uid 500); 28 Aug 2006 09:29:30 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 38808 invoked by uid 500); 28 Aug 2006 09:29:30 -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 38410 invoked by uid 99); 28 Aug 2006 09:29:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Aug 2006 02:29:28 -0700 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SUBJ_HAS_SPACES X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [217.144.149.34] (HELO TPN-EX01.PROJECT-NETWORK.COM) (217.144.149.34) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Aug 2006 02:29:27 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Subject: RE: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: problem with XML-RPC request using JMeter Date: Mon, 28 Aug 2006 10:29:01 +0100 Message-ID: <9EFC04356BBC4745B67A41B106F4A47A01BCD3E9@TPN-EX01.PROJECT-NETWORK.COM> In-Reply-To: <62645.125.16.130.66.1156735729.squirrel@209.10.209.38> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: problem with XML-RPC request using JMeter Thread-Index: AcbKUuMiOFdqFXixRxSAe9XbRK8RKQAMW1cg From: "Alex Turner" To: "JMeter Users List" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N In which case I really don't know. Maybe this is a question for the = apache user groups? Good luck! 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]=20 Sent: 28 August 2006 04:29 To: JMeter Users List Subject: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: TPN POSSIBLE = SPAM:RE: problem with XML-RPC request using JMeter 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 --=20 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 --=20 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 --=20 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 --=20 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 --=20 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.6/428 - Release Date: = 25/08/2006 =20 =20 --=20 No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.6/428 - Release Date: = 25/08/2006 =20 --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org