You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Noam Paz <no...@db.com> on 2007/03/09 14:03:27 UTC
Problems with WebService request
Hello,
This is just a rehash of the note(s) I sent 2 days ago, but I haven't seen any response, and I really could use some help with this.
What are the limitations on the soap message sent in the field Soap/XML-RPC Data?
More concrete:
We send a message containing an XML request to be executed. In this XML request there is a second XML request embedded in a CDATA section. See request 1 below.
JMeter seems to have problems with XML in the request. It can not process it and sends nothing. In the jmeter.log we see
2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The processing instruction target matching "[xX][mM][lL]" is not allowed.
2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
As a workaround we tried to put the offending XML request entirely as a CDATA section in our SOAP request (see request 2)
Again, JMeter can not process the request.
jmeter.log reveals following info:
2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The element type "string" must be terminated by the matching end-tag "</string>".
2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
Are we doing something wrong?
Do we stumble on limitations of JMeter?
Any ideas/workarounds?
Thanks!!
Request 1 - the original request
================================
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
</env:Header>
<env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
<string xsi:type="xsd:string"><?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope></string>
</m:execute>
</env:Body>
</env:Envelope>
Request 2 - the XML request is packed in the CDATA section
==========================================================
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
</env:Header>
<env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
<string xsi:type="xsd:string"><![CDATA[<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope>]]></string>
</m:execute>
</env:Body>
</env:Envelope>
--
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: My new listener
Posted by sebb <se...@gmail.com>.
Couple of things I forgot to mention:
JMeter requires Java 1.4 as a minimum.
Any add-ons need to support Java 1.4.
Also, it helps if the code has Javadoc for any new classes and data structures.
No need to document methods that override standard JMeter methods, but
it helps if new methods etc are documented.
Unit tests are also very helpful.
It's also useful to know if the add-on has been tested successfully in
non-GUI and remote mode.
S.
On 10/03/07, sebb <se...@gmail.com> wrote:
> Sounds very useful.
>
> Bucket seems fine as a name to me.
>
> I seem to remember a similar idea being discussed before, but it never
> got as far as being built, so this is very apt.
>
> If you want to contribute the code, then the normal route (after
> checking on the mailing list as you have already done) would be to
> create a Bugzilla enhancement issue describing the contribution.
>
> You can then re-open the issue and attach any necessary files to it.
>
> Any modified files (e.g. properties) should be provided as unified
> diff patches against the current SVN (branches/rel-2-2).
>
> New files should not be provided as patches.
> Please make sure the files include the ASF license header at the
> beginning (just look at an existing file).
>
> It would help a lot if some text could be provided for the manual as
> well; this could either be a patch, or a <component> section in the
> style of the existing entries in component_reference.xml which could
> then just be pasted in.
>
> S.
> On 10/03/07, James Bull <jb...@thoughtworks.com> wrote:
> > It's tentatively called Bucket listener which is probably not a good name.
> >
> > It provides information about the distribution of response times.
> >
> > You define a series of intervals and then it behaves in much the same way
> > as the summary element in the postprocessor menu only I've put it under
> > the listener menu. Each time a sample occurs it looks at the time and
> > increments the appropriate counter. I used a binary search to find the
> > correct interval so it shouldn't have too much effect on the amount of
> > load j-meter can generate even with a large number of intervals. It then
> > prints to the console window and the log file.
> >
> > You can specify the intervals manually in a table or you can just tell it
> > the upper and lower limits and the number of intervals you want and will
> > work them out itself.
> >
> > It uses the same property as the summariser to tell it when to report.
> >
> > I couldn't get it working as a separate jar file so I added the classes to
> > the apache core.jar
> >
> > The classes are
> > org.apache.jmeter.reporters.BucketListenerModel
> > org.apache.jmeter.reporters.BucketResultCollector
> >
> > org.apache.jmeter.visualizers.Bucket
> > org.apache.jmeter.visualizers.BucketSet
> > org.apache.jmeter.visualizers.BucketListener
> >
> > I would like to get this added to j-meter if possible. I want to know what
> > the procedure is for submitting this addition and what the standards for
> > acceptance are. I would also like to know if people think it is a good
> > idea and if they find it useful.
> >
> > My motivation in doing this was that I wanted to be able to run a large
> > number of samples (millions) against a website and have some knowledge of
> > response time distribution without having to store every result. I'm
> > reasonably pleased with it. I'm a tester rather than a programmer so my
> > code may well be a bit odd. I would be more than happy to receive
> > criticism of my code should someone have the time spare to have a look at
> > it.
> >
> > You can download the files from here if you are interested
> > http://www.box.net/p/james96046
> > There are two files one is a built ApacheJmeter_core.jar with the bucket
> > listener in it and the other is just the source for it.
> >
> > James
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: My new listener
Posted by sebb <se...@gmail.com>.
Sounds very useful.
Bucket seems fine as a name to me.
I seem to remember a similar idea being discussed before, but it never
got as far as being built, so this is very apt.
If you want to contribute the code, then the normal route (after
checking on the mailing list as you have already done) would be to
create a Bugzilla enhancement issue describing the contribution.
You can then re-open the issue and attach any necessary files to it.
Any modified files (e.g. properties) should be provided as unified
diff patches against the current SVN (branches/rel-2-2).
New files should not be provided as patches.
Please make sure the files include the ASF license header at the
beginning (just look at an existing file).
It would help a lot if some text could be provided for the manual as
well; this could either be a patch, or a <component> section in the
style of the existing entries in component_reference.xml which could
then just be pasted in.
S.
On 10/03/07, James Bull <jb...@thoughtworks.com> wrote:
> It's tentatively called Bucket listener which is probably not a good name.
>
> It provides information about the distribution of response times.
>
> You define a series of intervals and then it behaves in much the same way
> as the summary element in the postprocessor menu only I've put it under
> the listener menu. Each time a sample occurs it looks at the time and
> increments the appropriate counter. I used a binary search to find the
> correct interval so it shouldn't have too much effect on the amount of
> load j-meter can generate even with a large number of intervals. It then
> prints to the console window and the log file.
>
> You can specify the intervals manually in a table or you can just tell it
> the upper and lower limits and the number of intervals you want and will
> work them out itself.
>
> It uses the same property as the summariser to tell it when to report.
>
> I couldn't get it working as a separate jar file so I added the classes to
> the apache core.jar
>
> The classes are
> org.apache.jmeter.reporters.BucketListenerModel
> org.apache.jmeter.reporters.BucketResultCollector
>
> org.apache.jmeter.visualizers.Bucket
> org.apache.jmeter.visualizers.BucketSet
> org.apache.jmeter.visualizers.BucketListener
>
> I would like to get this added to j-meter if possible. I want to know what
> the procedure is for submitting this addition and what the standards for
> acceptance are. I would also like to know if people think it is a good
> idea and if they find it useful.
>
> My motivation in doing this was that I wanted to be able to run a large
> number of samples (millions) against a website and have some knowledge of
> response time distribution without having to store every result. I'm
> reasonably pleased with it. I'm a tester rather than a programmer so my
> code may well be a bit odd. I would be more than happy to receive
> criticism of my code should someone have the time spare to have a look at
> it.
>
> You can download the files from here if you are interested
> http://www.box.net/p/james96046
> There are two files one is a built ApacheJmeter_core.jar with the bucket
> listener in it and the other is just the source for it.
>
> James
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
My new listener
Posted by James Bull <jb...@thoughtworks.com>.
It's tentatively called Bucket listener which is probably not a good name.
It provides information about the distribution of response times.
You define a series of intervals and then it behaves in much the same way
as the summary element in the postprocessor menu only I've put it under
the listener menu. Each time a sample occurs it looks at the time and
increments the appropriate counter. I used a binary search to find the
correct interval so it shouldn't have too much effect on the amount of
load j-meter can generate even with a large number of intervals. It then
prints to the console window and the log file.
You can specify the intervals manually in a table or you can just tell it
the upper and lower limits and the number of intervals you want and will
work them out itself.
It uses the same property as the summariser to tell it when to report.
I couldn't get it working as a separate jar file so I added the classes to
the apache core.jar
The classes are
org.apache.jmeter.reporters.BucketListenerModel
org.apache.jmeter.reporters.BucketResultCollector
org.apache.jmeter.visualizers.Bucket
org.apache.jmeter.visualizers.BucketSet
org.apache.jmeter.visualizers.BucketListener
I would like to get this added to j-meter if possible. I want to know what
the procedure is for submitting this addition and what the standards for
acceptance are. I would also like to know if people think it is a good
idea and if they find it useful.
My motivation in doing this was that I wanted to be able to run a large
number of samples (millions) against a website and have some knowledge of
response time distribution without having to store every result. I'm
reasonably pleased with it. I'm a tester rather than a programmer so my
code may well be a bit odd. I would be more than happy to receive
criticism of my code should someone have the time spare to have a look at
it.
You can download the files from here if you are interested
http://www.box.net/p/james96046
There are two files one is a built ApacheJmeter_core.jar with the bucket
listener in it and the other is just the source for it.
James
Re: Problems with WebService request
Posted by sebb <se...@gmail.com>.
I'm guessing, but try removing the CDATA sections entirely.
I tried sending the amended XML to an Http echo server, and it does
not show any < etc - that must be happening at the Weblogic end.
I don't think this is a problem with JMeter.
S.
On 09/03/07, Noam Paz <no...@db.com> wrote:
> Hi,
> thanks for the suggestions.
>
> First to the suggestion quoting/protecting the ?xml and DOCTYPE sections:
> Yes, JMeter can process the request now, but it changes the content of the request in such a way that the server (Bea Weblogic 8.1.5) can not process it.
> It quotes the "<?xml " and "<!DOCTYPE " to "<?xml " and "<!DOCTYPE " and Weblogic throws a java.lang.ClassNotFoundException.
>
> About the suggestion to use the SOAP/XML-RPC Request instead: this has caused a java.lang.StringIndexOutOfBoundsException on the server. We are investigating on it.
>
> Any further suggestions are welcomed... :-)
>
> Thanks!
> Noam
>
>
>
>
>
> sebb <se...@gmail.com>
>
> 09.03.2007 14:51 To
> "JMeter Users List" <jm...@jakarta.apache.org>
> cc
> Please respond to
> "JMeter Users List" <jm...@jakarta.apache.org> Subject
> Re: Problems with WebService request
>
>
>
>
>
>
>
>
>
>
> I've just realised what the problem is: CDATA sections cannot be nested.
>
> You need to protect the ?xml and DOCTYPE section separately from the rest.
>
> i.e.
>
> <string xsi:type="xsd:string">
> <![CDATA[
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!DOCTYPE Envelope SYSTEM "Envelope.dtd">
> ]]>
> <Envelope> <Version>1</Version>
> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender>
> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver>
> <Content>
> <![CDATA[
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd">
> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId>
> <Application>20</Application> <Version>33</Version> </Header> <Order
> type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount>
> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security>
> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order>
> </OrderAmountRequest> ]]>
> </Content>
> </Envelope>
> </string>
>
> You can probably do the same with the Content CDATA - i.e. only
> enclose the xml and DOCTYPE parts rather than the whole lot.
>
> That will allow the request to be sent. However, whether it make sense
> to include these sections in a SOAP message, I have no idea.
>
> S.
>
> On 09/03/07, sebb <se...@gmail.com> wrote:
> > Can you try this using the SOAP/XML-RPC Request instead?
> >
> > That does not seem to care what contents is provided.
> >
> > On 09/03/07, Noam Paz <no...@db.com> wrote:
> > > Hello,
> > >
> > > This is just a rehash of the note(s) I sent 2 days ago, but I haven't seen any response, and I really could use some help with this.
> > >
> > >
> > > What are the limitations on the soap message sent in the field Soap/XML-RPC Data?
> > > More concrete:
> > > We send a message containing an XML request to be executed. In this XML request there is a second XML request embedded in a CDATA section. See request 1 below.
> > > JMeter seems to have problems with XML in the request. It can not process it and sends nothing. In the jmeter.log we see
> > >
> > > 2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The processing instruction target matching "[xX][mM][lL]" is not allowed.
> > > 2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
> > >
> > >
> > > As a workaround we tried to put the offending XML request entirely as a CDATA section in our SOAP request (see request 2)
> > >
> > >
> > > Again, JMeter can not process the request.
> > > jmeter.log reveals following info:
> > > 2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The element type "string" must be terminated by the matching end-tag "</string>".
> > > 2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
> > >
> > >
> > > Are we doing something wrong?
> > > Do we stumble on limitations of JMeter?
> > > Any ideas/workarounds?
> > > Thanks!!
> > >
> > >
> > >
> > > Request 1 - the original request
> > > ================================
> > >
> > > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > > <env:Header>
> > > </env:Header>
> > > <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> > > <m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
> > > <string xsi:type="xsd:string"><?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope></string>
> > > </m:execute>
> > > </env:Body>
> > > </env:Envelope>
> > >
> > >
> > > Request 2 - the XML request is packed in the CDATA section
> > > ==========================================================
> > >
> > > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > > <env:Header>
> > > </env:Header>
> > > <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> > > <m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
> > > <string xsi:type="xsd:string"><![CDATA[<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope>]]></string>
> > > </m:execute>
> > > </env:Body>
> > > </env:Envelope>
> > >
> > >
> > >
> > >
> > > --
> > >
> > > Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
> > >
> > > This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
>
>
> --
>
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Problems with WebService request
Posted by Noam Paz <no...@db.com>.
Hi,
thanks for the suggestions.
First to the suggestion quoting/protecting the ?xml and DOCTYPE sections:
Yes, JMeter can process the request now, but it changes the content of the request in such a way that the server (Bea Weblogic 8.1.5) can not process it.
It quotes the "<?xml " and "<!DOCTYPE " to "<?xml " and "<!DOCTYPE " and Weblogic throws a java.lang.ClassNotFoundException.
About the suggestion to use the SOAP/XML-RPC Request instead: this has caused a java.lang.StringIndexOutOfBoundsException on the server. We are investigating on it.
Any further suggestions are welcomed... :-)
Thanks!
Noam
sebb <se...@gmail.com>
09.03.2007 14:51 To
"JMeter Users List" <jm...@jakarta.apache.org>
cc
Please respond to
"JMeter Users List" <jm...@jakarta.apache.org> Subject
Re: Problems with WebService request
I've just realised what the problem is: CDATA sections cannot be nested.
You need to protect the ?xml and DOCTYPE section separately from the rest.
i.e.
<string xsi:type="xsd:string">
<![CDATA[
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE Envelope SYSTEM "Envelope.dtd">
]]>
<Envelope> <Version>1</Version>
<Sender><ApplicationId>HtmlClient</ApplicationId></Sender>
<Receiver><ApplicationId>FrontendService</ApplicationId></Receiver>
<Content>
<![CDATA[
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd">
<OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId>
<Application>20</Application> <Version>33</Version> </Header> <Order
type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount>
<Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security>
<Quantity>1</Quantity> <TradeType>A</TradeType> </Order>
</OrderAmountRequest> ]]>
</Content>
</Envelope>
</string>
You can probably do the same with the Content CDATA - i.e. only
enclose the xml and DOCTYPE parts rather than the whole lot.
That will allow the request to be sent. However, whether it make sense
to include these sections in a SOAP message, I have no idea.
S.
On 09/03/07, sebb <se...@gmail.com> wrote:
> Can you try this using the SOAP/XML-RPC Request instead?
>
> That does not seem to care what contents is provided.
>
> On 09/03/07, Noam Paz <no...@db.com> wrote:
> > Hello,
> >
> > This is just a rehash of the note(s) I sent 2 days ago, but I haven't seen any response, and I really could use some help with this.
> >
> >
> > What are the limitations on the soap message sent in the field Soap/XML-RPC Data?
> > More concrete:
> > We send a message containing an XML request to be executed. In this XML request there is a second XML request embedded in a CDATA section. See request 1 below.
> > JMeter seems to have problems with XML in the request. It can not process it and sends nothing. In the jmeter.log we see
> >
> > 2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The processing instruction target matching "[xX][mM][lL]" is not allowed.
> > 2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
> >
> >
> > As a workaround we tried to put the offending XML request entirely as a CDATA section in our SOAP request (see request 2)
> >
> >
> > Again, JMeter can not process the request.
> > jmeter.log reveals following info:
> > 2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The element type "string" must be terminated by the matching end-tag "</string>".
> > 2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
> >
> >
> > Are we doing something wrong?
> > Do we stumble on limitations of JMeter?
> > Any ideas/workarounds?
> > Thanks!!
> >
> >
> >
> > Request 1 - the original request
> > ================================
> >
> > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > <env:Header>
> > </env:Header>
> > <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> > <m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
> > <string xsi:type="xsd:string"><?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope></string>
> > </m:execute>
> > </env:Body>
> > </env:Envelope>
> >
> >
> > Request 2 - the XML request is packed in the CDATA section
> > ==========================================================
> >
> > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > <env:Header>
> > </env:Header>
> > <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> > <m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
> > <string xsi:type="xsd:string"><![CDATA[<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope>]]></string>
> > </m:execute>
> > </env:Body>
> > </env:Envelope>
> >
> >
> >
> >
> > --
> >
> > Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
> >
> > This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
--
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Problems with WebService request
Posted by sebb <se...@gmail.com>.
I've just realised what the problem is: CDATA sections cannot be nested.
You need to protect the ?xml and DOCTYPE section separately from the rest.
i.e.
<string xsi:type="xsd:string">
<![CDATA[
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE Envelope SYSTEM "Envelope.dtd">
]]>
<Envelope> <Version>1</Version>
<Sender><ApplicationId>HtmlClient</ApplicationId></Sender>
<Receiver><ApplicationId>FrontendService</ApplicationId></Receiver>
<Content>
<![CDATA[
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd">
<OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId>
<Application>20</Application> <Version>33</Version> </Header> <Order
type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount>
<Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security>
<Quantity>1</Quantity> <TradeType>A</TradeType> </Order>
</OrderAmountRequest> ]]>
</Content>
</Envelope>
</string>
You can probably do the same with the Content CDATA - i.e. only
enclose the xml and DOCTYPE parts rather than the whole lot.
That will allow the request to be sent. However, whether it make sense
to include these sections in a SOAP message, I have no idea.
S.
On 09/03/07, sebb <se...@gmail.com> wrote:
> Can you try this using the SOAP/XML-RPC Request instead?
>
> That does not seem to care what contents is provided.
>
> On 09/03/07, Noam Paz <no...@db.com> wrote:
> > Hello,
> >
> > This is just a rehash of the note(s) I sent 2 days ago, but I haven't seen any response, and I really could use some help with this.
> >
> >
> > What are the limitations on the soap message sent in the field Soap/XML-RPC Data?
> > More concrete:
> > We send a message containing an XML request to be executed. In this XML request there is a second XML request embedded in a CDATA section. See request 1 below.
> > JMeter seems to have problems with XML in the request. It can not process it and sends nothing. In the jmeter.log we see
> >
> > 2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The processing instruction target matching "[xX][mM][lL]" is not allowed.
> > 2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
> >
> >
> > As a workaround we tried to put the offending XML request entirely as a CDATA section in our SOAP request (see request 2)
> >
> >
> > Again, JMeter can not process the request.
> > jmeter.log reveals following info:
> > 2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The element type "string" must be terminated by the matching end-tag "</string>".
> > 2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
> >
> >
> > Are we doing something wrong?
> > Do we stumble on limitations of JMeter?
> > Any ideas/workarounds?
> > Thanks!!
> >
> >
> >
> > Request 1 - the original request
> > ================================
> >
> > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > <env:Header>
> > </env:Header>
> > <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> > <m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
> > <string xsi:type="xsd:string"><?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope></string>
> > </m:execute>
> > </env:Body>
> > </env:Envelope>
> >
> >
> > Request 2 - the XML request is packed in the CDATA section
> > ==========================================================
> >
> > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > <env:Header>
> > </env:Header>
> > <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> > <m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
> > <string xsi:type="xsd:string"><![CDATA[<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope>]]></string>
> > </m:execute>
> > </env:Body>
> > </env:Envelope>
> >
> >
> >
> >
> > --
> >
> > Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
> >
> > This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Problems with WebService request
Posted by sebb <se...@gmail.com>.
Can you try this using the SOAP/XML-RPC Request instead?
That does not seem to care what contents is provided.
On 09/03/07, Noam Paz <no...@db.com> wrote:
> Hello,
>
> This is just a rehash of the note(s) I sent 2 days ago, but I haven't seen any response, and I really could use some help with this.
>
>
> What are the limitations on the soap message sent in the field Soap/XML-RPC Data?
> More concrete:
> We send a message containing an XML request to be executed. In this XML request there is a second XML request embedded in a CDATA section. See request 1 below.
> JMeter seems to have problems with XML in the request. It can not process it and sends nothing. In the jmeter.log we see
>
> 2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The processing instruction target matching "[xX][mM][lL]" is not allowed.
> 2007/03/07 15:44:59 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
>
>
> As a workaround we tried to put the offending XML request entirely as a CDATA section in our SOAP request (see request 2)
>
>
> Again, JMeter can not process the request.
> jmeter.log reveals following info:
> 2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: Error processing data: The element type "string" must be terminated by the matching end-tag "</string>".
> 2007/03/07 11:11:58 WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=Could not create document; msg=]
>
>
> Are we doing something wrong?
> Do we stumble on limitations of JMeter?
> Any ideas/workarounds?
> Thanks!!
>
>
>
> Request 1 - the original request
> ================================
>
> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <env:Header>
> </env:Header>
> <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> <m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
> <string xsi:type="xsd:string"><?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope></string>
> </m:execute>
> </env:Body>
> </env:Envelope>
>
>
> Request 2 - the XML request is packed in the CDATA section
> ==========================================================
>
> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <env:Header>
> </env:Header>
> <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> <m:execute xmlns:m="http://mcbs.eur.deuba.com/service/ServiceRouter">
> <string xsi:type="xsd:string"><![CDATA[<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Envelope SYSTEM "Envelope.dtd"><Envelope> <Version>1</Version> <Sender><ApplicationId>HtmlClient</ApplicationId></Sender> <Receiver><ApplicationId>FrontendService</ApplicationId></Receiver> <Content> <![CDATA[ <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE OrderAmountRequest SYSTEM "DTD/OrderAmountRequest.dtd"> <OrderAmountRequest reduce="1"> <Header> <EntityId>DBK</EntityId> <Application>20</Application> <Version>33</Version> </Header> <Order type="1"> <Portfolio> <Id>1234567</Id> </Portfolio> <SecAccount> <Id>1234567</Id> </SecAccount> <Security> <Id>710000</Id> </Security> <Quantity>1</Quantity> <TradeType>A</TradeType> </Order> </OrderAmountRequest> ]]> </Content> </Envelope>]]></string>
> </m:execute>
> </env:Body>
> </env:Envelope>
>
>
>
>
> --
>
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org