You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by ad...@spikesource.com on 2006/08/28 05:28:49 UTC
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.
<?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
--
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
RE: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: TPN POSSIBLE SPAM:RE: problem with XML-RPC request using JMeter
Posted by Alex Turner <Al...@Project-Network.com>.
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]
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.
<?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
--
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/428 - Release Date: 25/08/2006
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org