jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Turner" <Alex.Tur...@Project-Network.com>
Subject RE: TPN POSSIBLE SPAM:RE: problem with XML-RPC request using JMeter
Date Sat, 26 Aug 2006 20:48:31 GMT
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.



<?xml version="1.0"?>

<methodCall>

<methodName>myMethod</methodName>

<params>

<param>

<value>12</value>

</param>

<param>

<value>sdfd</value>

</param>

<param>

<value>213213</value>

</param>

<param>

<value>91</value>

</param>

<param>

<value>df</value>

</param>

<param>

<value>0</value>

</param>

<param>

<value>123</value></param>

</params>

</methodCall>



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



<?xml version="1.0"?>

<methodCall>

<methodName>myMethod</methodName>

<params>

<param>

<value>12</value>

</param>

<param>

<value>sdfd</value>

</param>

<param>

<value>213213</value>

</param>

<param>

<value>91</value>

</param>

<param>

<value>df</value>

</param>

<param>

<value>0</value>

</param>

<param>

<value>123</value></param>

</params>

</methodCall>



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


Mime
View raw message