JMeter › JMeter - User

SOAP data repeated across different Webservice samplers

Classic

List

Threaded

17 messages Options

Ivan Rancati

SOAP data repeated across different Webservice samplers

I have a very simple test plan for a Web Service, which looks like this

Thread group (1 loop - 1 thread)
User defined variables (http server name and port)
HTTP Authorization Manager
WebService(SOAP) Request
Response Assertion
WebService(SOAP) Request
WebService(SOAP) Request
WebService(SOAP) Request
View Results Tree
Assertion Results

For the 4 requests, server ip, port number, path and SOAP Action are the
same
The Soap/XML-RPC data changes only in the <email> part

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:findCustomerByEmail
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
<email xsi:type="xsd:string">[hidden email]
</email>
</ns1:findCustomerByEmail>
</soapenv:Body>
</soapenv:Envelope>

When I run the test case, the same SOAP content is sent for all the 4
requests. Is this a known issue?
I have verified the behaviour by running through a proxy.

In general, it looks like there is something strange with the WebService
requests: for example, if I change the order of the requests, I have to
close and reopen the test plan for the change to take effect.

Server is running Debian Linux, and the webservice is Axis.
On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5

thanks

--
Ivan Rancati
SharpMind QA

--
Ivan Rancati
SharpMind QA

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

sebb-2-2

Re: SOAP data repeated across different Webservice samplers

Sounds like a bug.

Please can you raise a Bugzilla issue, and attach a test-case etc?

Thanks.

On 14/02/06, Ivan Rancati <[hidden email]> wrote:

> I have a very simple test plan for a Web Service, which looks like this
>
> Thread group (1 loop - 1 thread)
> User defined variables (http server name and port)
> HTTP Authorization Manager
> WebService(SOAP) Request
> Response Assertion
> WebService(SOAP) Request
> WebService(SOAP) Request
> WebService(SOAP) Request
> View Results Tree
> Assertion Results
>
> For the 4 requests, server ip, port number, path and SOAP Action are the
> same
> The Soap/XML-RPC data changes only in the <email> part
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <ns1:findCustomerByEmail
> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> <email xsi:type="xsd:string">[hidden email]
> </email>
> </ns1:findCustomerByEmail>
> </soapenv:Body>
> </soapenv:Envelope>
>
> When I run the test case, the same SOAP content is sent for all the 4
> requests. Is this a known issue?
> I have verified the behaviour by running through a proxy.
>
> In general, it looks like there is something strange with the WebService
> requests: for example, if I change the order of the requests, I have to
> close and reopen the test plan for the change to take effect.
>
> Server is running Debian Linux, and the webservice is Axis.
> On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
>
>
> thanks
>
> --
> Ivan Rancati
> SharpMind QA
>
>
> --
> Ivan Rancati
> SharpMind QA
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Ivan Rancati

Re: SOAP data repeated across different Webservice samplers

In reply to this post by Ivan Rancati

In the meantime, I found out that the problem is the "Memory Cache"
option in the sampler
I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
should cache the Soap request only across different threads for the same
sampler, not across all samplers. Or have I misunderstood it?

thanks
Ivan

Re: SOAP data repeated across different Webservice samplers

sebb
Tue, 14 Feb 2006 03:31:08 -0800

Sounds like a bug.

Please can you raise a Bugzilla issue, and attach a test-case etc?

Thanks.

On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:

> I have a very simple test plan for a Web Service, which looks like this
>
> Thread group (1 loop - 1 thread)
> User defined variables (http server name and port)
> HTTP Authorization Manager
> WebService(SOAP) Request
> Response Assertion
> WebService(SOAP) Request
> WebService(SOAP) Request
> WebService(SOAP) Request
> View Results Tree
> Assertion Results
>
> For the 4 requests, server ip, port number, path and SOAP Action are the
> same
> The Soap/XML-RPC data changes only in the <email> part
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <http://schemas.xmlsoap.org/soap/envelope/%22>;
> xmlns:xsd="http://www.w3.org/2001/XMLSchema" <http://www.w3.org/2001/XMLSchema%22>;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <http://www.w3.org/2001/XMLSchema-instance%22>;>
> <soapenv:Body>
> <ns1:findCustomerByEmail
> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <http://schemas.xmlsoap.org/soap/encoding/%22>;
> xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> <email xsi:type="xsd:string">[EMAIL PROTECTED]
> </email>
> </ns1:findCustomerByEmail>
> </soapenv:Body>
> </soapenv:Envelope>
>
> When I run the test case, the same SOAP content is sent for all the 4
> requests. Is this a known issue?
> I have verified the behaviour by running through a proxy.
>
> In general, it looks like there is something strange with the WebService
> requests: for example, if I change the order of the requests, I have to
> close and reopen the test plan for the change to take effect.
>
> Server is running Debian Linux, and the webservice is Axis.
> On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
>
>
> thanks
>
> --
> Ivan Rancati
> SharpMind QA
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Peter Lin

Re: SOAP data repeated across different Webservice samplers

the memory cache is very simple and stupid, and was meant as a way to
improve JMeter's ability to generate higher loads. Basically, the idea was
to send the same SOAP message as fast as possible to stress a server.

thanks for filing the bug, I probably won't have time to add the enhancement
for atleast 2-3 months.

peter

On 2/14/06, Ivan Rancati <[hidden email]> wrote:

>
> In the meantime, I found out that the problem is the "Memory Cache"
> option in the sampler
> I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
> should cache the Soap request only across different threads for the same
> sampler, not across all samplers. Or have I misunderstood it?
>
> thanks
> Ivan
>
>
> Re: SOAP data repeated across different Webservice samplers
>
> sebb
> Tue, 14 Feb 2006 03:31:08 -0800
>
> Sounds like a bug.
>
> Please can you raise a Bugzilla issue, and attach a test-case etc?
>
> Thanks.
>
> On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
> > I have a very simple test plan for a Web Service, which looks like this
> >
> > Thread group (1 loop - 1 thread)
> > User defined variables (http server name and port)
> > HTTP Authorization Manager
> > WebService(SOAP) Request
> > Response Assertion
> > WebService(SOAP) Request
> > WebService(SOAP) Request
> > WebService(SOAP) Request
> > View Results Tree
> > Assertion Results
> >
> > For the 4 requests, server ip, port number, path and SOAP Action are the
> > same
> > The Soap/XML-RPC data changes only in the <email> part
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <
> http://schemas.xmlsoap.org/soap/envelope/%22>;
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema" <
> http://www.w3.org/2001/XMLSchema%22>;
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <
> http://www.w3.org/2001/XMLSchema-instance%22>;>
> > <soapenv:Body>
> > <ns1:findCustomerByEmail
> > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <
> http://schemas.xmlsoap.org/soap/encoding/%22>;
> > xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> > <email xsi:type="xsd:string">[EMAIL PROTECTED]
> > </email>
> > </ns1:findCustomerByEmail>
> > </soapenv:Body>
> > </soapenv:Envelope>
> >
> > When I run the test case, the same SOAP content is sent for all the 4
> > requests. Is this a known issue?
> > I have verified the behaviour by running through a proxy.
> >
> > In general, it looks like there is something strange with the WebService
> > requests: for example, if I change the order of the requests, I have to
> > close and reopen the test plan for the change to take effect.
> >
> > Server is running Debian Linux, and the webservice is Axis.
> > On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
> >
> >
> > thanks
> >
> > --
> > Ivan Rancati
> > SharpMind QA
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

sebb-2-2

Re: SOAP data repeated across different Webservice samplers

I may have some time to apply fixes in a shorter time span.

However I don't have any experience of using SOAP so I would need help
from users to provide test cases etc.

S.
On 14/02/06, Peter Lin <[hidden email]> wrote:

> the memory cache is very simple and stupid, and was meant as a way to
> improve JMeter's ability to generate higher loads. Basically, the idea was
> to send the same SOAP message as fast as possible to stress a server.
>
> thanks for filing the bug, I probably won't have time to add the enhancement
> for atleast 2-3 months.
>
> peter
>
>
> On 2/14/06, Ivan Rancati <[hidden email]> wrote:
> >
> > In the meantime, I found out that the problem is the "Memory Cache"
> > option in the sampler
> > I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
> > should cache the Soap request only across different threads for the same
> > sampler, not across all samplers. Or have I misunderstood it?
> >
> > thanks
> > Ivan
> >
> >
> > Re: SOAP data repeated across different Webservice samplers
> >
> > sebb
> > Tue, 14 Feb 2006 03:31:08 -0800
> >
> > Sounds like a bug.
> >
> > Please can you raise a Bugzilla issue, and attach a test-case etc?
> >
> > Thanks.
> >
> > On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
> > > I have a very simple test plan for a Web Service, which looks like this
> > >
> > > Thread group (1 loop - 1 thread)
> > > User defined variables (http server name and port)
> > > HTTP Authorization Manager
> > > WebService(SOAP) Request
> > > Response Assertion
> > > WebService(SOAP) Request
> > > WebService(SOAP) Request
> > > WebService(SOAP) Request
> > > View Results Tree
> > > Assertion Results
> > >
> > > For the 4 requests, server ip, port number, path and SOAP Action are the
> > > same
> > > The Soap/XML-RPC data changes only in the <email> part
> > >
> > > <soapenv:Envelope
> > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <
> > http://schemas.xmlsoap.org/soap/envelope/%22>;
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema" <
> > http://www.w3.org/2001/XMLSchema%22>;
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <
> > http://www.w3.org/2001/XMLSchema-instance%22>;>
> > > <soapenv:Body>
> > > <ns1:findCustomerByEmail
> > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <
> > http://schemas.xmlsoap.org/soap/encoding/%22>;
> > > xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> > > <email xsi:type="xsd:string">[EMAIL PROTECTED]
> > > </email>
> > > </ns1:findCustomerByEmail>
> > > </soapenv:Body>
> > > </soapenv:Envelope>
> > >
> > > When I run the test case, the same SOAP content is sent for all the 4
> > > requests. Is this a known issue?
> > > I have verified the behaviour by running through a proxy.
> > >
> > > In general, it looks like there is something strange with the WebService
> > > requests: for example, if I change the order of the requests, I have to
> > > close and reopen the test plan for the change to take effect.
> > >
> > > Server is running Debian Linux, and the webservice is Axis.
> > > On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
> > >
> > >
> > > thanks
> > >
> > > --
> > > Ivan Rancati
> > > SharpMind QA
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Ivan Rancati

Re: SOAP data repeated across different Webservice samplers

In reply to this post by Ivan Rancati

I'd like to help, with
a) attaching a simple test plan to bug 38640
b) if needed, testing the fix before it's released.

What I'd need to know for (a) is if there is some Axis web service
publicly accessible over the Internet. Does not need to be very fancy

>
> Subject:
> Re: SOAP data repeated across different Webservice samplers
> From:
> sebb <[hidden email]>
> Date:
> Tue, 14 Feb 2006 14:52:42 +0000
> To:
> JMeter Users List <[hidden email]>
>
> To:
> JMeter Users List <[hidden email]>
>
>
> I may have some time to apply fixes in a shorter time span.
>
> However I don't have any experience of using SOAP so I would need help
> from users to provide test cases etc.
>
> S.
> On 14/02/06, Peter Lin <[hidden email]> wrote:
>
>> the memory cache is very simple and stupid, and was meant as a way to
>> improve JMeter's ability to generate higher loads. Basically, the idea was
>> to send the same SOAP message as fast as possible to stress a server.
>>
>> thanks for filing the bug, I probably won't have time to add the enhancement
>> for atleast 2-3 months.
>>
>> peter
>>
>>
>> On 2/14/06, Ivan Rancati <[hidden email]> wrote:
>>
>>> In the meantime, I found out that the problem is the "Memory Cache"
>>> option in the sampler
>>> I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
>>> should cache the Soap request only across different threads for the same
>>> sampler, not across all samplers. Or have I misunderstood it?
>>>
>>> thanks
>>> Ivan
>>>
>>>
>>> Re: SOAP data repeated across different Webservice samplers
>>>
>>> sebb
>>> Tue, 14 Feb 2006 03:31:08 -0800
>>>
>>> Sounds like a bug.
>>>
>>> Please can you raise a Bugzilla issue, and attach a test-case etc?
>>>
>>> Thanks.
>>>
>>> On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
>>>
>>>> I have a very simple test plan for a Web Service, which looks like this
>>>>
>>>> Thread group (1 loop - 1 thread)
>>>> User defined variables (http server name and port)
>>>> HTTP Authorization Manager
>>>> WebService(SOAP) Request
>>>> Response Assertion
>>>> WebService(SOAP) Request
>>>> WebService(SOAP) Request
>>>> WebService(SOAP) Request
>>>> View Results Tree
>>>> Assertion Results
>>>>
>>>> For the 4 requests, server ip, port number, path and SOAP Action are the
>>>> same
>>>> The Soap/XML-RPC data changes only in the <email> part
>>>>
>>>> <soapenv:Envelope
>>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <
>>>>
>>> http://schemas.xmlsoap.org/soap/envelope/%22>;
>>>
>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" <
>>>>
>>> http://www.w3.org/2001/XMLSchema%22>;
>>>
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <
>>>>
>>> http://www.w3.org/2001/XMLSchema-instance%22>;>
>>>
>>>> <soapenv:Body>
>>>> <ns1:findCustomerByEmail
>>>> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <
>>>>
>>> http://schemas.xmlsoap.org/soap/encoding/%22>;
>>>
>>>> xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
>>>> <email xsi:type="xsd:string">[EMAIL PROTECTED]
>>>> </email>
>>>> </ns1:findCustomerByEmail>
>>>> </soapenv:Body>
>>>> </soapenv:Envelope>
>>>>
>>>> When I run the test case, the same SOAP content is sent for all the 4
>>>> requests. Is this a known issue?
>>>> I have verified the behaviour by running through a proxy.
>>>>
>>>> In general, it looks like there is something strange with the WebService
>>>> requests: for example, if I change the order of the requests, I have to
>>>> close and reopen the test plan for the change to take effect.
>>>>
>>>> Server is running Debian Linux, and the webservice is Axis.
>>>> On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
>>>>
>>>>
>>>> thanks
>>>>
>>>> --
>>>> Ivan Rancati
>>>> SharpMind QA
>>>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

sebb-2-2

Re: SOAP data repeated across different Webservice samplers

I had a quick look at the cache last night - I think it uses the file
name as the key.

I can add some debug to the code to show which cache entry is being
used. That might help pin down the problem. I'll give that a go
tonight hopefully and create a new nightly build.

Seems to me that the cache can be shared by all threads, so long as
the content of each entry does not vary.

S.
On 15/02/06, Ivan Rancati <[hidden email]> wrote:

> I'd like to help, with
> a) attaching a simple test plan to bug 38640
> b) if needed, testing the fix before it's released.
>
> What I'd need to know for (a) is if there is some Axis web service
> publicly accessible over the Internet. Does not need to be very fancy
>
>
>
> >
> > Subject:
> > Re: SOAP data repeated across different Webservice samplers
> > From:
> > sebb <[hidden email]>
> > Date:
> > Tue, 14 Feb 2006 14:52:42 +0000
> > To:
> > JMeter Users List <[hidden email]>
> >
> > To:
> > JMeter Users List <[hidden email]>
> >
> >
> > I may have some time to apply fixes in a shorter time span.
> >
> > However I don't have any experience of using SOAP so I would need help
> > from users to provide test cases etc.
> >
> > S.
> > On 14/02/06, Peter Lin <[hidden email]> wrote:
> >
> >> the memory cache is very simple and stupid, and was meant as a way to
> >> improve JMeter's ability to generate higher loads. Basically, the idea was
> >> to send the same SOAP message as fast as possible to stress a server.
> >>
> >> thanks for filing the bug, I probably won't have time to add the enhancement
> >> for atleast 2-3 months.
> >>
> >> peter
> >>
> >>
> >> On 2/14/06, Ivan Rancati <[hidden email]> wrote:
> >>
> >>> In the meantime, I found out that the problem is the "Memory Cache"
> >>> option in the sampler
> >>> I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
> >>> should cache the Soap request only across different threads for the same
> >>> sampler, not across all samplers. Or have I misunderstood it?
> >>>
> >>> thanks
> >>> Ivan
> >>>
> >>>
> >>> Re: SOAP data repeated across different Webservice samplers
> >>>
> >>> sebb
> >>> Tue, 14 Feb 2006 03:31:08 -0800
> >>>
> >>> Sounds like a bug.
> >>>
> >>> Please can you raise a Bugzilla issue, and attach a test-case etc?
> >>>
> >>> Thanks.
> >>>
> >>> On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> I have a very simple test plan for a Web Service, which looks like this
> >>>>
> >>>> Thread group (1 loop - 1 thread)
> >>>> User defined variables (http server name and port)
> >>>> HTTP Authorization Manager
> >>>> WebService(SOAP) Request
> >>>> Response Assertion
> >>>> WebService(SOAP) Request
> >>>> WebService(SOAP) Request
> >>>> WebService(SOAP) Request
> >>>> View Results Tree
> >>>> Assertion Results
> >>>>
> >>>> For the 4 requests, server ip, port number, path and SOAP Action are the
> >>>> same
> >>>> The Soap/XML-RPC data changes only in the <email> part
> >>>>
> >>>> <soapenv:Envelope
> >>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <
> >>>>
> >>> http://schemas.xmlsoap.org/soap/envelope/%22>;
> >>>
> >>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" <
> >>>>
> >>> http://www.w3.org/2001/XMLSchema%22>;
> >>>
> >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <
> >>>>
> >>> http://www.w3.org/2001/XMLSchema-instance%22>;>
> >>>
> >>>> <soapenv:Body>
> >>>> <ns1:findCustomerByEmail
> >>>> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <
> >>>>
> >>> http://schemas.xmlsoap.org/soap/encoding/%22>;
> >>>
> >>>> xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> >>>> <email xsi:type="xsd:string">[EMAIL PROTECTED]
> >>>> </email>
> >>>> </ns1:findCustomerByEmail>
> >>>> </soapenv:Body>
> >>>> </soapenv:Envelope>
> >>>>
> >>>> When I run the test case, the same SOAP content is sent for all the 4
> >>>> requests. Is this a known issue?
> >>>> I have verified the behaviour by running through a proxy.
> >>>>
> >>>> In general, it looks like there is something strange with the WebService
> >>>> requests: for example, if I change the order of the requests, I have to
> >>>> close and reopen the test plan for the change to take effect.
> >>>>
> >>>> Server is running Debian Linux, and the webservice is Axis.
> >>>> On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
> >>>>
> >>>>
> >>>> thanks
> >>>>
> >>>> --
> >>>> Ivan Rancati
> >>>> SharpMind QA
> >>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Peter Lin

Re: SOAP data repeated across different Webservice samplers

:)

yeah, it just uses the filename, rather than the thread name. it's probably
easy enough to do threadName + filename, or just threadName.

peter

On 2/15/06, sebb <[hidden email]> wrote:

>
> I had a quick look at the cache last night - I think it uses the file
> name as the key.
>
> I can add some debug to the code to show which cache entry is being
> used. That might help pin down the problem. I'll give that a go
> tonight hopefully and create a new nightly build.
>
> Seems to me that the cache can be shared by all threads, so long as
> the content of each entry does not vary.
>
> S.
> On 15/02/06, Ivan Rancati <[hidden email]> wrote:
> > I'd like to help, with
> > a) attaching a simple test plan to bug 38640
> > b) if needed, testing the fix before it's released.
> >
> > What I'd need to know for (a) is if there is some Axis web service
> > publicly accessible over the Internet. Does not need to be very fancy
> >
> >
> >
> > >
> > > Subject:
> > > Re: SOAP data repeated across different Webservice samplers
> > > From:
> > > sebb <[hidden email]>
> > > Date:
> > > Tue, 14 Feb 2006 14:52:42 +0000
> > > To:
> > > JMeter Users List <[hidden email]>
> > >
> > > To:
> > > JMeter Users List <[hidden email]>
> > >
> > >
> > > I may have some time to apply fixes in a shorter time span.
> > >
> > > However I don't have any experience of using SOAP so I would need help
> > > from users to provide test cases etc.
> > >
> > > S.
> > > On 14/02/06, Peter Lin <[hidden email]> wrote:
> > >
> > >> the memory cache is very simple and stupid, and was meant as a way to
> > >> improve JMeter's ability to generate higher loads. Basically, the
> idea was
> > >> to send the same SOAP message as fast as possible to stress a server.
> > >>
> > >> thanks for filing the bug, I probably won't have time to add the
> enhancement
> > >> for atleast 2-3 months.
> > >>
> > >> peter
> > >>
> > >>
> > >> On 2/14/06, Ivan Rancati <[hidden email]> wrote:
> > >>
> > >>> In the meantime, I found out that the problem is the "Memory Cache"
> > >>> option in the sampler
> > >>> I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
> > >>> should cache the Soap request only across different threads for the
> same
> > >>> sampler, not across all samplers. Or have I misunderstood it?
> > >>>
> > >>> thanks
> > >>> Ivan
> > >>>
> > >>>
> > >>> Re: SOAP data repeated across different Webservice samplers
> > >>>
> > >>> sebb
> > >>> Tue, 14 Feb 2006 03:31:08 -0800
> > >>>
> > >>> Sounds like a bug.
> > >>>
> > >>> Please can you raise a Bugzilla issue, and attach a test-case etc?
> > >>>
> > >>> Thanks.
> > >>>
> > >>> On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
> > >>>
> > >>>> I have a very simple test plan for a Web Service, which looks like
> this
> > >>>>
> > >>>> Thread group (1 loop - 1 thread)
> > >>>> User defined variables (http server name and port)
> > >>>> HTTP Authorization Manager
> > >>>> WebService(SOAP) Request
> > >>>> Response Assertion
> > >>>> WebService(SOAP) Request
> > >>>> WebService(SOAP) Request
> > >>>> WebService(SOAP) Request
> > >>>> View Results Tree
> > >>>> Assertion Results
> > >>>>
> > >>>> For the 4 requests, server ip, port number, path and SOAP Action
> are the
> > >>>> same
> > >>>> The Soap/XML-RPC data changes only in the <email> part
> > >>>>
> > >>>> <soapenv:Envelope
> > >>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <
> > >>>>
> > >>> http://schemas.xmlsoap.org/soap/envelope/%22>;
> > >>>
> > >>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" <
> > >>>>
> > >>> http://www.w3.org/2001/XMLSchema%22>;
> > >>>
> > >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <
> > >>>>
> > >>> http://www.w3.org/2001/XMLSchema-instance%22>;>
> > >>>
> > >>>> <soapenv:Body>
> > >>>> <ns1:findCustomerByEmail
> > >>>> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <
> > >>>>
> > >>> http://schemas.xmlsoap.org/soap/encoding/%22>;
> > >>>
> > >>>> xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> > >>>> <email xsi:type="xsd:string">[EMAIL
> PROTECTED]
> > >>>> </email>
> > >>>> </ns1:findCustomerByEmail>
> > >>>> </soapenv:Body>
> > >>>> </soapenv:Envelope>
> > >>>>
> > >>>> When I run the test case, the same SOAP content is sent for all the
> 4
> > >>>> requests. Is this a known issue?
> > >>>> I have verified the behaviour by running through a proxy.
> > >>>>
> > >>>> In general, it looks like there is something strange with the
> WebService
> > >>>> requests: for example, if I change the order of the requests, I
> have to
> > >>>> close and reopen the test plan for the change to take effect.
> > >>>>
> > >>>> Server is running Debian Linux, and the webservice is Axis.
> > >>>> On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
> > >>>>
> > >>>>
> > >>>> thanks
> > >>>>
> > >>>> --
> > >>>> Ivan Rancati
> > >>>> SharpMind QA
> > >>>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

sebb-2-2

Re: SOAP data repeated across different Webservice samplers

ThreadName alone would not work, as there may be multiple samplers per thread.

However filename alone should surely be enough - unless the file
content changes during a run, which would not be a good idea.

This is why I don't understand what's happening at present...

S.
On 15/02/06, Peter Lin <[hidden email]> wrote:

> :)
>
> yeah, it just uses the filename, rather than the thread name. it's probably
> easy enough to do threadName + filename, or just threadName.
>
> peter
>
>
> On 2/15/06, sebb <[hidden email]> wrote:
> >
> > I had a quick look at the cache last night - I think it uses the file
> > name as the key.
> >
> > I can add some debug to the code to show which cache entry is being
> > used. That might help pin down the problem. I'll give that a go
> > tonight hopefully and create a new nightly build.
> >
> > Seems to me that the cache can be shared by all threads, so long as
> > the content of each entry does not vary.
> >
> > S.
> > On 15/02/06, Ivan Rancati <[hidden email]> wrote:
> > > I'd like to help, with
> > > a) attaching a simple test plan to bug 38640
> > > b) if needed, testing the fix before it's released.
> > >
> > > What I'd need to know for (a) is if there is some Axis web service
> > > publicly accessible over the Internet. Does not need to be very fancy
> > >
> > >
> > >
> > > >
> > > > Subject:
> > > > Re: SOAP data repeated across different Webservice samplers
> > > > From:
> > > > sebb <[hidden email]>
> > > > Date:
> > > > Tue, 14 Feb 2006 14:52:42 +0000
> > > > To:
> > > > JMeter Users List <[hidden email]>
> > > >
> > > > To:
> > > > JMeter Users List <[hidden email]>
> > > >
> > > >
> > > > I may have some time to apply fixes in a shorter time span.
> > > >
> > > > However I don't have any experience of using SOAP so I would need help
> > > > from users to provide test cases etc.
> > > >
> > > > S.
> > > > On 14/02/06, Peter Lin <[hidden email]> wrote:
> > > >
> > > >> the memory cache is very simple and stupid, and was meant as a way to
> > > >> improve JMeter's ability to generate higher loads. Basically, the
> > idea was
> > > >> to send the same SOAP message as fast as possible to stress a server.
> > > >>
> > > >> thanks for filing the bug, I probably won't have time to add the
> > enhancement
> > > >> for atleast 2-3 months.
> > > >>
> > > >> peter
> > > >>
> > > >>
> > > >> On 2/14/06, Ivan Rancati <[hidden email]> wrote:
> > > >>
> > > >>> In the meantime, I found out that the problem is the "Memory Cache"
> > > >>> option in the sampler
> > > >>> I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
> > > >>> should cache the Soap request only across different threads for the
> > same
> > > >>> sampler, not across all samplers. Or have I misunderstood it?
> > > >>>
> > > >>> thanks
> > > >>> Ivan
> > > >>>
> > > >>>
> > > >>> Re: SOAP data repeated across different Webservice samplers
> > > >>>
> > > >>> sebb
> > > >>> Tue, 14 Feb 2006 03:31:08 -0800
> > > >>>
> > > >>> Sounds like a bug.
> > > >>>
> > > >>> Please can you raise a Bugzilla issue, and attach a test-case etc?
> > > >>>
> > > >>> Thanks.
> > > >>>
> > > >>> On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
> > > >>>
> > > >>>> I have a very simple test plan for a Web Service, which looks like
> > this
> > > >>>>
> > > >>>> Thread group (1 loop - 1 thread)
> > > >>>> User defined variables (http server name and port)
> > > >>>> HTTP Authorization Manager
> > > >>>> WebService(SOAP) Request
> > > >>>> Response Assertion
> > > >>>> WebService(SOAP) Request
> > > >>>> WebService(SOAP) Request
> > > >>>> WebService(SOAP) Request
> > > >>>> View Results Tree
> > > >>>> Assertion Results
> > > >>>>
> > > >>>> For the 4 requests, server ip, port number, path and SOAP Action
> > are the
> > > >>>> same
> > > >>>> The Soap/XML-RPC data changes only in the <email> part
> > > >>>>
> > > >>>> <soapenv:Envelope
> > > >>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <
> > > >>>>
> > > >>> http://schemas.xmlsoap.org/soap/envelope/%22>;
> > > >>>
> > > >>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" <
> > > >>>>
> > > >>> http://www.w3.org/2001/XMLSchema%22>;
> > > >>>
> > > >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <
> > > >>>>
> > > >>> http://www.w3.org/2001/XMLSchema-instance%22>;>
> > > >>>
> > > >>>> <soapenv:Body>
> > > >>>> <ns1:findCustomerByEmail
> > > >>>> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <
> > > >>>>
> > > >>> http://schemas.xmlsoap.org/soap/encoding/%22>;
> > > >>>
> > > >>>> xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> > > >>>> <email xsi:type="xsd:string">[EMAIL
> > PROTECTED]
> > > >>>> </email>
> > > >>>> </ns1:findCustomerByEmail>
> > > >>>> </soapenv:Body>
> > > >>>> </soapenv:Envelope>
> > > >>>>
> > > >>>> When I run the test case, the same SOAP content is sent for all the
> > 4
> > > >>>> requests. Is this a known issue?
> > > >>>> I have verified the behaviour by running through a proxy.
> > > >>>>
> > > >>>> In general, it looks like there is something strange with the
> > WebService
> > > >>>> requests: for example, if I change the order of the requests, I
> > have to
> > > >>>> close and reopen the test plan for the change to take effect.
> > > >>>>
> > > >>>> Server is running Debian Linux, and the webservice is Axis.
> > > >>>> On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
> > > >>>>
> > > >>>>
> > > >>>> thanks
> > > >>>>
> > > >>>> --
> > > >>>> Ivan Rancati
> > > >>>> SharpMind QA
> > > >>>>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

sebb-2-2

Re: SOAP data repeated across different Webservice samplers

I've added some logging to the WebService sampler, which shows the
file names used.

The code is in the nightly build of Feb 15.

Perhaps you could give it a try?

S.
On 15/02/06, sebb <[hidden email]> wrote:

> ThreadName alone would not work, as there may be multiple samplers per thread.
>
> However filename alone should surely be enough - unless the file
> content changes during a run, which would not be a good idea.
>
> This is why I don't understand what's happening at present...
>
> S.
> On 15/02/06, Peter Lin <[hidden email]> wrote:
> > :)
> >
> > yeah, it just uses the filename, rather than the thread name. it's probably
> > easy enough to do threadName + filename, or just threadName.
> >
> > peter
> >
> >
> > On 2/15/06, sebb <[hidden email]> wrote:
> > >
> > > I had a quick look at the cache last night - I think it uses the file
> > > name as the key.
> > >
> > > I can add some debug to the code to show which cache entry is being
> > > used. That might help pin down the problem. I'll give that a go
> > > tonight hopefully and create a new nightly build.
> > >
> > > Seems to me that the cache can be shared by all threads, so long as
> > > the content of each entry does not vary.
> > >
> > > S.
> > > On 15/02/06, Ivan Rancati <[hidden email]> wrote:
> > > > I'd like to help, with
> > > > a) attaching a simple test plan to bug 38640
> > > > b) if needed, testing the fix before it's released.
> > > >
> > > > What I'd need to know for (a) is if there is some Axis web service
> > > > publicly accessible over the Internet. Does not need to be very fancy
> > > >
> > > >
> > > >
> > > > >
> > > > > Subject:
> > > > > Re: SOAP data repeated across different Webservice samplers
> > > > > From:
> > > > > sebb <[hidden email]>
> > > > > Date:
> > > > > Tue, 14 Feb 2006 14:52:42 +0000
> > > > > To:
> > > > > JMeter Users List <[hidden email]>
> > > > >
> > > > > To:
> > > > > JMeter Users List <[hidden email]>
> > > > >
> > > > >
> > > > > I may have some time to apply fixes in a shorter time span.
> > > > >
> > > > > However I don't have any experience of using SOAP so I would need help
> > > > > from users to provide test cases etc.
> > > > >
> > > > > S.
> > > > > On 14/02/06, Peter Lin <[hidden email]> wrote:
> > > > >
> > > > >> the memory cache is very simple and stupid, and was meant as a way to
> > > > >> improve JMeter's ability to generate higher loads. Basically, the
> > > idea was
> > > > >> to send the same SOAP message as fast as possible to stress a server.
> > > > >>
> > > > >> thanks for filing the bug, I probably won't have time to add the
> > > enhancement
> > > > >> for atleast 2-3 months.
> > > > >>
> > > > >> peter
> > > > >>
> > > > >>
> > > > >> On 2/14/06, Ivan Rancati <[hidden email]> wrote:
> > > > >>
> > > > >>> In the meantime, I found out that the problem is the "Memory Cache"
> > > > >>> option in the sampler
> > > > >>> I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
> > > > >>> should cache the Soap request only across different threads for the
> > > same
> > > > >>> sampler, not across all samplers. Or have I misunderstood it?
> > > > >>>
> > > > >>> thanks
> > > > >>> Ivan
> > > > >>>
> > > > >>>
> > > > >>> Re: SOAP data repeated across different Webservice samplers
> > > > >>>
> > > > >>> sebb
> > > > >>> Tue, 14 Feb 2006 03:31:08 -0800
> > > > >>>
> > > > >>> Sounds like a bug.
> > > > >>>
> > > > >>> Please can you raise a Bugzilla issue, and attach a test-case etc?
> > > > >>>
> > > > >>> Thanks.
> > > > >>>
> > > > >>> On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
> > > > >>>
> > > > >>>> I have a very simple test plan for a Web Service, which looks like
> > > this
> > > > >>>>
> > > > >>>> Thread group (1 loop - 1 thread)
> > > > >>>> User defined variables (http server name and port)
> > > > >>>> HTTP Authorization Manager
> > > > >>>> WebService(SOAP) Request
> > > > >>>> Response Assertion
> > > > >>>> WebService(SOAP) Request
> > > > >>>> WebService(SOAP) Request
> > > > >>>> WebService(SOAP) Request
> > > > >>>> View Results Tree
> > > > >>>> Assertion Results
> > > > >>>>
> > > > >>>> For the 4 requests, server ip, port number, path and SOAP Action
> > > are the
> > > > >>>> same
> > > > >>>> The Soap/XML-RPC data changes only in the <email> part
> > > > >>>>
> > > > >>>> <soapenv:Envelope
> > > > >>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <
> > > > >>>>
> > > > >>> http://schemas.xmlsoap.org/soap/envelope/%22>;
> > > > >>>
> > > > >>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" <
> > > > >>>>
> > > > >>> http://www.w3.org/2001/XMLSchema%22>;
> > > > >>>
> > > > >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <
> > > > >>>>
> > > > >>> http://www.w3.org/2001/XMLSchema-instance%22>;>
> > > > >>>
> > > > >>>> <soapenv:Body>
> > > > >>>> <ns1:findCustomerByEmail
> > > > >>>> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <
> > > > >>>>
> > > > >>> http://schemas.xmlsoap.org/soap/encoding/%22>;
> > > > >>>
> > > > >>>> xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> > > > >>>> <email xsi:type="xsd:string">[EMAIL
> > > PROTECTED]
> > > > >>>> </email>
> > > > >>>> </ns1:findCustomerByEmail>
> > > > >>>> </soapenv:Body>
> > > > >>>> </soapenv:Envelope>
> > > > >>>>
> > > > >>>> When I run the test case, the same SOAP content is sent for all the
> > > 4
> > > > >>>> requests. Is this a known issue?
> > > > >>>> I have verified the behaviour by running through a proxy.
> > > > >>>>
> > > > >>>> In general, it looks like there is something strange with the
> > > WebService
> > > > >>>> requests: for example, if I change the order of the requests, I
> > > have to
> > > > >>>> close and reopen the test plan for the change to take effect.
> > > > >>>>
> > > > >>>> Server is running Debian Linux, and the webservice is Axis.
> > > > >>>> On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
> > > > >>>>
> > > > >>>>
> > > > >>>> thanks
> > > > >>>>
> > > > >>>> --
> > > > >>>> Ivan Rancati
> > > > >>>> SharpMind QA
> > > > >>>>
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

sebb-2-2

Re: SOAP data repeated across different Webservice samplers

Just had another look at the code:

The problem is that the key only applies to file-based XML.

If the XML is provided on the screen, then of course it does not have
a filename, and the key that is generated for the pool is the empty
string...

S.
On 15/02/06, sebb <[hidden email]> wrote:

> I've added some logging to the WebService sampler, which shows the
> file names used.
>
> The code is in the nightly build of Feb 15.
>
> Perhaps you could give it a try?
>
> S.
> On 15/02/06, sebb <[hidden email]> wrote:
> > ThreadName alone would not work, as there may be multiple samplers per thread.
> >
> > However filename alone should surely be enough - unless the file
> > content changes during a run, which would not be a good idea.
> >
> > This is why I don't understand what's happening at present...
> >
> > S.
> > On 15/02/06, Peter Lin <[hidden email]> wrote:
> > > :)
> > >
> > > yeah, it just uses the filename, rather than the thread name. it's probably
> > > easy enough to do threadName + filename, or just threadName.
> > >
> > > peter
> > >
> > >
> > > On 2/15/06, sebb <[hidden email]> wrote:
> > > >
> > > > I had a quick look at the cache last night - I think it uses the file
> > > > name as the key.
> > > >
> > > > I can add some debug to the code to show which cache entry is being
> > > > used. That might help pin down the problem. I'll give that a go
> > > > tonight hopefully and create a new nightly build.
> > > >
> > > > Seems to me that the cache can be shared by all threads, so long as
> > > > the content of each entry does not vary.
> > > >
> > > > S.
> > > > On 15/02/06, Ivan Rancati <[hidden email]> wrote:
> > > > > I'd like to help, with
> > > > > a) attaching a simple test plan to bug 38640
> > > > > b) if needed, testing the fix before it's released.
> > > > >
> > > > > What I'd need to know for (a) is if there is some Axis web service
> > > > > publicly accessible over the Internet. Does not need to be very fancy
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Subject:
> > > > > > Re: SOAP data repeated across different Webservice samplers
> > > > > > From:
> > > > > > sebb <[hidden email]>
> > > > > > Date:
> > > > > > Tue, 14 Feb 2006 14:52:42 +0000
> > > > > > To:
> > > > > > JMeter Users List <[hidden email]>
> > > > > >
> > > > > > To:
> > > > > > JMeter Users List <[hidden email]>
> > > > > >
> > > > > >
> > > > > > I may have some time to apply fixes in a shorter time span.
> > > > > >
> > > > > > However I don't have any experience of using SOAP so I would need help
> > > > > > from users to provide test cases etc.
> > > > > >
> > > > > > S.
> > > > > > On 14/02/06, Peter Lin <[hidden email]> wrote:
> > > > > >
> > > > > >> the memory cache is very simple and stupid, and was meant as a way to
> > > > > >> improve JMeter's ability to generate higher loads. Basically, the
> > > > idea was
> > > > > >> to send the same SOAP message as fast as possible to stress a server.
> > > > > >>
> > > > > >> thanks for filing the bug, I probably won't have time to add the
> > > > enhancement
> > > > > >> for atleast 2-3 months.
> > > > > >>
> > > > > >> peter
> > > > > >>
> > > > > >>
> > > > > >> On 2/14/06, Ivan Rancati <[hidden email]> wrote:
> > > > > >>
> > > > > >>> In the meantime, I found out that the problem is the "Memory Cache"
> > > > > >>> option in the sampler
> > > > > >>> I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
> > > > > >>> should cache the Soap request only across different threads for the
> > > > same
> > > > > >>> sampler, not across all samplers. Or have I misunderstood it?
> > > > > >>>
> > > > > >>> thanks
> > > > > >>> Ivan
> > > > > >>>
> > > > > >>>
> > > > > >>> Re: SOAP data repeated across different Webservice samplers
> > > > > >>>
> > > > > >>> sebb
> > > > > >>> Tue, 14 Feb 2006 03:31:08 -0800
> > > > > >>>
> > > > > >>> Sounds like a bug.
> > > > > >>>
> > > > > >>> Please can you raise a Bugzilla issue, and attach a test-case etc?
> > > > > >>>
> > > > > >>> Thanks.
> > > > > >>>
> > > > > >>> On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
> > > > > >>>
> > > > > >>>> I have a very simple test plan for a Web Service, which looks like
> > > > this
> > > > > >>>>
> > > > > >>>> Thread group (1 loop - 1 thread)
> > > > > >>>> User defined variables (http server name and port)
> > > > > >>>> HTTP Authorization Manager
> > > > > >>>> WebService(SOAP) Request
> > > > > >>>> Response Assertion
> > > > > >>>> WebService(SOAP) Request
> > > > > >>>> WebService(SOAP) Request
> > > > > >>>> WebService(SOAP) Request
> > > > > >>>> View Results Tree
> > > > > >>>> Assertion Results
> > > > > >>>>
> > > > > >>>> For the 4 requests, server ip, port number, path and SOAP Action
> > > > are the
> > > > > >>>> same
> > > > > >>>> The Soap/XML-RPC data changes only in the <email> part
> > > > > >>>>
> > > > > >>>> <soapenv:Envelope
> > > > > >>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <
> > > > > >>>>
> > > > > >>> http://schemas.xmlsoap.org/soap/envelope/%22>;
> > > > > >>>
> > > > > >>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" <
> > > > > >>>>
> > > > > >>> http://www.w3.org/2001/XMLSchema%22>;
> > > > > >>>
> > > > > >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <
> > > > > >>>>
> > > > > >>> http://www.w3.org/2001/XMLSchema-instance%22>;>
> > > > > >>>
> > > > > >>>> <soapenv:Body>
> > > > > >>>> <ns1:findCustomerByEmail
> > > > > >>>> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <
> > > > > >>>>
> > > > > >>> http://schemas.xmlsoap.org/soap/encoding/%22>;
> > > > > >>>
> > > > > >>>> xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> > > > > >>>> <email xsi:type="xsd:string">[EMAIL
> > > > PROTECTED]
> > > > > >>>> </email>
> > > > > >>>> </ns1:findCustomerByEmail>
> > > > > >>>> </soapenv:Body>
> > > > > >>>> </soapenv:Envelope>
> > > > > >>>>
> > > > > >>>> When I run the test case, the same SOAP content is sent for all the
> > > > 4
> > > > > >>>> requests. Is this a known issue?
> > > > > >>>> I have verified the behaviour by running through a proxy.
> > > > > >>>>
> > > > > >>>> In general, it looks like there is something strange with the
> > > > WebService
> > > > > >>>> requests: for example, if I change the order of the requests, I
> > > > have to
> > > > > >>>> close and reopen the test plan for the change to take effect.
> > > > > >>>>
> > > > > >>>> Server is running Debian Linux, and the webservice is Axis.
> > > > > >>>> On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> thanks
> > > > > >>>>
> > > > > >>>> --
> > > > > >>>> Ivan Rancati
> > > > > >>>> SharpMind QA
> > > > > >>>>
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > > >
> > >
> > >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

sebb-2-2

Re: SOAP data repeated across different Webservice samplers

I think I've now fixed this - the code has been checked in to the 2.1 branch.

I'll do a "nightly" build a later today or tomorrow.

S.
On 18/02/06, sebb <[hidden email]> wrote:

> Just had another look at the code:
>
> The problem is that the key only applies to file-based XML.
>
> If the XML is provided on the screen, then of course it does not have
> a filename, and the key that is generated for the pool is the empty
> string...
>
> S.
> On 15/02/06, sebb <[hidden email]> wrote:
> > I've added some logging to the WebService sampler, which shows the
> > file names used.
> >
> > The code is in the nightly build of Feb 15.
> >
> > Perhaps you could give it a try?
> >
> > S.
> > On 15/02/06, sebb <[hidden email]> wrote:
> > > ThreadName alone would not work, as there may be multiple samplers per thread.
> > >
> > > However filename alone should surely be enough - unless the file
> > > content changes during a run, which would not be a good idea.
> > >
> > > This is why I don't understand what's happening at present...
> > >
> > > S.
> > > On 15/02/06, Peter Lin <[hidden email]> wrote:
> > > > :)
> > > >
> > > > yeah, it just uses the filename, rather than the thread name. it's probably
> > > > easy enough to do threadName + filename, or just threadName.
> > > >
> > > > peter
> > > >
> > > >
> > > > On 2/15/06, sebb <[hidden email]> wrote:
> > > > >
> > > > > I had a quick look at the cache last night - I think it uses the file
> > > > > name as the key.
> > > > >
> > > > > I can add some debug to the code to show which cache entry is being
> > > > > used. That might help pin down the problem. I'll give that a go
> > > > > tonight hopefully and create a new nightly build.
> > > > >
> > > > > Seems to me that the cache can be shared by all threads, so long as
> > > > > the content of each entry does not vary.
> > > > >
> > > > > S.
> > > > > On 15/02/06, Ivan Rancati <[hidden email]> wrote:
> > > > > > I'd like to help, with
> > > > > > a) attaching a simple test plan to bug 38640
> > > > > > b) if needed, testing the fix before it's released.
> > > > > >
> > > > > > What I'd need to know for (a) is if there is some Axis web service
> > > > > > publicly accessible over the Internet. Does not need to be very fancy
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Subject:
> > > > > > > Re: SOAP data repeated across different Webservice samplers
> > > > > > > From:
> > > > > > > sebb <[hidden email]>
> > > > > > > Date:
> > > > > > > Tue, 14 Feb 2006 14:52:42 +0000
> > > > > > > To:
> > > > > > > JMeter Users List <[hidden email]>
> > > > > > >
> > > > > > > To:
> > > > > > > JMeter Users List <[hidden email]>
> > > > > > >
> > > > > > >
> > > > > > > I may have some time to apply fixes in a shorter time span.
> > > > > > >
> > > > > > > However I don't have any experience of using SOAP so I would need help
> > > > > > > from users to provide test cases etc.
> > > > > > >
> > > > > > > S.
> > > > > > > On 14/02/06, Peter Lin <[hidden email]> wrote:
> > > > > > >
> > > > > > >> the memory cache is very simple and stupid, and was meant as a way to
> > > > > > >> improve JMeter's ability to generate higher loads. Basically, the
> > > > > idea was
> > > > > > >> to send the same SOAP message as fast as possible to stress a server.
> > > > > > >>
> > > > > > >> thanks for filing the bug, I probably won't have time to add the
> > > > > enhancement
> > > > > > >> for atleast 2-3 months.
> > > > > > >>
> > > > > > >> peter
> > > > > > >>
> > > > > > >>
> > > > > > >> On 2/14/06, Ivan Rancati <[hidden email]> wrote:
> > > > > > >>
> > > > > > >>> In the meantime, I found out that the problem is the "Memory Cache"
> > > > > > >>> option in the sampler
> > > > > > >>> I logged a P3 bug (38640) anyway, as I believe the "Memory cache"
> > > > > > >>> should cache the Soap request only across different threads for the
> > > > > same
> > > > > > >>> sampler, not across all samplers. Or have I misunderstood it?
> > > > > > >>>
> > > > > > >>> thanks
> > > > > > >>> Ivan
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> Re: SOAP data repeated across different Webservice samplers
> > > > > > >>>
> > > > > > >>> sebb
> > > > > > >>> Tue, 14 Feb 2006 03:31:08 -0800
> > > > > > >>>
> > > > > > >>> Sounds like a bug.
> > > > > > >>>
> > > > > > >>> Please can you raise a Bugzilla issue, and attach a test-case etc?
> > > > > > >>>
> > > > > > >>> Thanks.
> > > > > > >>>
> > > > > > >>> On 14/02/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
> > > > > > >>>
> > > > > > >>>> I have a very simple test plan for a Web Service, which looks like
> > > > > this
> > > > > > >>>>
> > > > > > >>>> Thread group (1 loop - 1 thread)
> > > > > > >>>> User defined variables (http server name and port)
> > > > > > >>>> HTTP Authorization Manager
> > > > > > >>>> WebService(SOAP) Request
> > > > > > >>>> Response Assertion
> > > > > > >>>> WebService(SOAP) Request
> > > > > > >>>> WebService(SOAP) Request
> > > > > > >>>> WebService(SOAP) Request
> > > > > > >>>> View Results Tree
> > > > > > >>>> Assertion Results
> > > > > > >>>>
> > > > > > >>>> For the 4 requests, server ip, port number, path and SOAP Action
> > > > > are the
> > > > > > >>>> same
> > > > > > >>>> The Soap/XML-RPC data changes only in the <email> part
> > > > > > >>>>
> > > > > > >>>> <soapenv:Envelope
> > > > > > >>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" <
> > > > > > >>>>
> > > > > > >>> http://schemas.xmlsoap.org/soap/envelope/%22>;
> > > > > > >>>
> > > > > > >>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" <
> > > > > > >>>>
> > > > > > >>> http://www.w3.org/2001/XMLSchema%22>;
> > > > > > >>>
> > > > > > >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <
> > > > > > >>>>
> > > > > > >>> http://www.w3.org/2001/XMLSchema-instance%22>;>
> > > > > > >>>
> > > > > > >>>> <soapenv:Body>
> > > > > > >>>> <ns1:findCustomerByEmail
> > > > > > >>>> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" <
> > > > > > >>>>
> > > > > > >>> http://schemas.xmlsoap.org/soap/encoding/%22>;
> > > > > > >>>
> > > > > > >>>> xmlns:ns1="urn://mobility-platform.de/mpcustomerdb/">
> > > > > > >>>> <email xsi:type="xsd:string">[EMAIL
> > > > > PROTECTED]
> > > > > > >>>> </email>
> > > > > > >>>> </ns1:findCustomerByEmail>
> > > > > > >>>> </soapenv:Body>
> > > > > > >>>> </soapenv:Envelope>
> > > > > > >>>>
> > > > > > >>>> When I run the test case, the same SOAP content is sent for all the
> > > > > 4
> > > > > > >>>> requests. Is this a known issue?
> > > > > > >>>> I have verified the behaviour by running through a proxy.
> > > > > > >>>>
> > > > > > >>>> In general, it looks like there is something strange with the
> > > > > WebService
> > > > > > >>>> requests: for example, if I change the order of the requests, I
> > > > > have to
> > > > > > >>>> close and reopen the test plan for the change to take effect.
> > > > > > >>>>
> > > > > > >>>> Server is running Debian Linux, and the webservice is Axis.
> > > > > > >>>> On the client, I am running Suse 9.3, Jmeter 2.1.1 and JDK 1.5
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>> thanks
> > > > > > >>>>
> > > > > > >>>> --
> > > > > > >>>> Ivan Rancati
> > > > > > >>>> SharpMind QA
> > > > > > >>>>
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: [hidden email]
> > > > > > For additional commands, e-mail: [hidden email]
> > > > > >
> > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Ivan Rancati

Re: SOAP data repeated across different Webservice samplers

Thanks a lot for the fix
I have tried the nightly build, and the fix is working correctly, both
for requests with a file and requests with online xml.

By the way, I have seen a problem with SOAP requests in the nightly
build 2-1.20060220 that is not present in 2.1.1:
at least for requests with online XML, the "Request" tab in View Results
tree does not show the SOAP request.

best regards

Re: SOAP data repeated across different Webservice samplers

sebb
Sat, 18 Feb 2006 13:46:37 -0800

I think I've now fixed this - the code has been checked in to the 2.1 branch.

I'll do a "nightly" build a later today or tomorrow.

S.
On 18/02/06, sebb <[EMAIL PROTECTED]> wrote:
> Just had another look at the code:
>
> The problem is that the key only applies to file-based XML.
>
> If the XML is provided on the screen, then of course it does not have
> a filename, and the key that is generated for the pool is the empty
> string...

--
Ivan Rancati
SharpMind QA

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

sebb-2-2

Re: SOAP data repeated across different Webservice samplers

On 20/02/06, Ivan Rancati <[hidden email]> wrote:
> Thanks a lot for the fix
> I have tried the nightly build, and the fix is working correctly, both
> for requests with a file and requests with online xml.

Great.

> By the way, I have seen a problem with SOAP requests in the nightly
> build 2-1.20060220 that is not present in 2.1.1:
> at least for requests with online XML, the "Request" tab in View Results
> tree does not show the SOAP request.

I made a change in this area, because it looked like the URL details
were being repeated in the request pane. Perhaps I got it wrong.

What do you see in the Request tab now?

S.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Tarun Khurana

Multipart data handling of Jmeter

In reply to this post by Ivan Rancati

Hi,

Can anybody tell me how Jmeter handles the multipart data? E.g. I have a
javascript which captures the contents of the screen and gives me the
consolidated data in the next screen. But when I start recording using the
proxy server, the application gives an exception.

Can anybody help in this context

Regards
Tarun

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

sebb-2-2

Re: Multipart data handling of Jmeter

Which application gives the Exception?

If it is JMeter, then please raise a Bugzilla issue.

If it is the application under test, then report the problem to the
application developers.

S.
On 21/02/06, Tarun Khurana <[hidden email]> wrote:

> Hi,
>
> Can anybody tell me how Jmeter handles the multipart data? E.g. I have a
> javascript which captures the contents of the screen and gives me the
> consolidated data in the next screen. But when I start recording using the
> proxy server, the application gives an exception.
>
>
> Can anybody help in this context
>
> Regards
> Tarun
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Tarun Khurana

RE: Multipart data handling of Jmeter

We are using the spring framework, and using the Multipartresolver class and
then the application is not able to grab the data

Regards
Tarun

-----Original Message-----
From: sebb [mailto:[hidden email]]
Sent: Tuesday, February 21, 2006 4:31 PM
To: JMeter Users List
Subject: Re: Multipart data handling of Jmeter

Which application gives the Exception?

If it is JMeter, then please raise a Bugzilla issue.

If it is the application under test, then report the problem to the
application developers.

S.
On 21/02/06, Tarun Khurana <[hidden email]> wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]