You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Deepak Shetty <sh...@gmail.com> on 2010/08/02 18:46:21 UTC
Re: jmeter and webflow: How to get another execution-Parameter for
every single thread
hi
is this the first step? Do you have a cookie manager? Do you have follow
redirects instead of redirect automatically?
If not it sounds like your application has a bug that doesnt allow it to
work under concurrent access. You can experiment with different (> 1 second
diff between threads) ramp up times and see (if it starts working correctly
then it probably is a problem with your app)
regards
deepak
On Mon, Aug 2, 2010 at 7:20 AM, Leis, Matthias - SID-NLKM <
Matthias.Leis@sid.sachsen.de> wrote:
> Hi,
>
> I am currently testing a Spring Webflow Application. The URLs look like
> http://localhost:8080/spring/main-flow?execution=e1s1
> The initial request is http://localhost:8080/spring/main-flow, which
> responds with a HTTP Status Code 302 which redirects to
> http://localhost:8080/spring/main-flow?execution=e1s1.
> When I start my test with more than one thread, every thread gets the
> same URLs. So the application doesn't really execute anything (e.g.
> Database access) the second time the URL is called, but returns only the
> stored views (because the URL is always the same).
>
> The behaviour using a browser is different. The first instance gets
> http://localhost:8080/spring/main-flow?execution=e1s1, the second
> instance gets http://localhost:8080/spring/main-flow?execution=e2s1
> (notice e2s1 instead of e1s1) and so on and the application really
> executes database accesses, web service calls and so on.
>
> So my question is: Does anybody have an idea, how to achieve, that the
> first thread gets e1s1, the second thread e2s1 and so on.
>
> Thanks, any help is appreciated!
>
> Regards,
>
> Matthias
>
>
>
AW: jmeter and webflow: How to get another execution-Parameter for every single thread
Posted by "Leis, Matthias - SID-NLKM" <Ma...@sid.sachsen.de>.
Hi,
Your example helped a lot, thanks! I started to build a smaller test according to your script and now it works. I don't know what exactly was wrong, but now it works.
Thanks :)
Matthias
Staatsbetrieb Sächsische Informatik Dienste -
Niederlassung Kamenz
Macherstr. 63
01917 Kamenz
E-Mail: Matthias.Leis@sid.sachsen.de
-----Ursprüngliche Nachricht-----
Von: jmeter-user-return-31002-Matthias.Leis=sid.sachsen.de@jakarta.apache.org [mailto:jmeter-user-return-31002-Matthias.Leis=sid.sachsen.de@jakarta.apache.org] Im Auftrag von Deepak Shetty
Gesendet: Mittwoch, 4. August 2010 19:17
An: JMeter Users List
Betreff: Re: jmeter and webflow: How to get another execution-Parameter for every single thread
Hi
did the sample script I uploaded help?
It looks like you might be making a mistake on how you have written your
test. You might need to upload a stripped down version somewhere and share
the link.
regards
deepak
On Tue, Aug 3, 2010 at 11:52 PM, Leis, Matthias - SID-NLKM <
Matthias.Leis@sid.sachsen.de> wrote:
> Hi Deepak,
>
> Yes, I have a Cookie Manager and follow redirects.
> Setting a ramp time doesn't make a difference.
>
>
> >hi
> >is this the first step? Do you have a cookie manager? Do you have follow
> >redirects instead of redirect automatically?
> >
> >If not it sounds like your application has a bug that doesnt allow it to
> >work under concurrent access. You can experiment with different (> 1
> second
> >diff between threads) ramp up times and see (if it starts working
> correctly
> >then it probably is a problem with your app)
> >
> >regards
> >deepak
>
> Hi,
>
> The 302 always redirects from one execution-parameter to another. It's the
> only thing, that changes in the URL. But yes, it's always the same.
> Startpage: e1s1, first click: e2s1 and so on. So for my testplan, it's
> rather static.
>
> >Hi Tibo,
> >
> >Your 302 redirects always on same page, or is it dynamic ?
> >So that you just have to exact the url from it... as usual ?
> >
> >Tibo
>
> The general problem is, that after the intial call of the application per
> http://localhost:8080/spring/main-flow
> The application has to redirect me to
> http://localhost:8080/spring/main-flow?execution=e1s1. I can't just call
> this URL myself, because the application "doesn't know me" yet. But every
> thread gets the same redirect.
>
> Regards
> Matthias
> -----Ursprüngliche Nachricht-----
> Von: jmeter-user-return-30951-Matthias.Leis=sid.sachsen.de@
> jakarta.apache.org [mailto:jmeter-user-return-30951-Matthias.Leis=
> sid.sachsen.de@jakarta.apache.org] Im Auftrag von Thibaut Raballand
> Gesendet: Montag, 2. August 2010 23:49
> An: JMeter Users List
> Betreff: Re: jmeter and webflow: How to get another execution-Parameter for
> every single thread
>
> Hi,
>
> Your 302 redirects always on same page, or is it dynamic ?
> So that you just have to exact the url from it... as usual ?
>
> Tibo
>
> On Mon, Aug 2, 2010 at 18:46, Deepak Shetty <sh...@gmail.com> wrote:
>
> > hi
> > is this the first step? Do you have a cookie manager? Do you have follow
> > redirects instead of redirect automatically?
> >
> > If not it sounds like your application has a bug that doesnt allow it to
> > work under concurrent access. You can experiment with different (> 1
> second
> > diff between threads) ramp up times and see (if it starts working
> correctly
> > then it probably is a problem with your app)
> >
> > regards
> > deepak
> >
> >
> >
> >
> > On Mon, Aug 2, 2010 at 7:20 AM, Leis, Matthias - SID-NLKM <
> > Matthias.Leis@sid.sachsen.de> wrote:
> >
> > > Hi,
> > >
> > > I am currently testing a Spring Webflow Application. The URLs look like
> > > http://localhost:8080/spring/main-flow?execution=e1s1
> > > The initial request is http://localhost:8080/spring/main-flow, which
> > > responds with a HTTP Status Code 302 which redirects to
> > > http://localhost:8080/spring/main-flow?execution=e1s1.
> > > When I start my test with more than one thread, every thread gets the
> > > same URLs. So the application doesn't really execute anything (e.g.
> > > Database access) the second time the URL is called, but returns only
> the
> > > stored views (because the URL is always the same).
> > >
> > > The behaviour using a browser is different. The first instance gets
> > > http://localhost:8080/spring/main-flow?execution=e1s1, the second
> > > instance gets http://localhost:8080/spring/main-flow?execution=e2s1
> > > (notice e2s1 instead of e1s1) and so on and the application really
> > > executes database accesses, web service calls and so on.
> > >
> > > So my question is: Does anybody have an idea, how to achieve, that the
> > > first thread gets e1s1, the second thread e2s1 and so on.
> > >
> > > Thanks, any help is appreciated!
> > >
> > > Regards,
> > >
> > > Matthias
> > >
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> 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: jmeter and webflow: How to get another execution-Parameter for
every single thread
Posted by Deepak Shetty <sh...@gmail.com>.
Hi
did the sample script I uploaded help?
It looks like you might be making a mistake on how you have written your
test. You might need to upload a stripped down version somewhere and share
the link.
regards
deepak
On Tue, Aug 3, 2010 at 11:52 PM, Leis, Matthias - SID-NLKM <
Matthias.Leis@sid.sachsen.de> wrote:
> Hi Deepak,
>
> Yes, I have a Cookie Manager and follow redirects.
> Setting a ramp time doesn't make a difference.
>
>
> >hi
> >is this the first step? Do you have a cookie manager? Do you have follow
> >redirects instead of redirect automatically?
> >
> >If not it sounds like your application has a bug that doesnt allow it to
> >work under concurrent access. You can experiment with different (> 1
> second
> >diff between threads) ramp up times and see (if it starts working
> correctly
> >then it probably is a problem with your app)
> >
> >regards
> >deepak
>
> Hi,
>
> The 302 always redirects from one execution-parameter to another. It's the
> only thing, that changes in the URL. But yes, it's always the same.
> Startpage: e1s1, first click: e2s1 and so on. So for my testplan, it's
> rather static.
>
> >Hi Tibo,
> >
> >Your 302 redirects always on same page, or is it dynamic ?
> >So that you just have to exact the url from it... as usual ?
> >
> >Tibo
>
> The general problem is, that after the intial call of the application per
> http://localhost:8080/spring/main-flow
> The application has to redirect me to
> http://localhost:8080/spring/main-flow?execution=e1s1. I can't just call
> this URL myself, because the application "doesn't know me" yet. But every
> thread gets the same redirect.
>
> Regards
> Matthias
> -----Ursprüngliche Nachricht-----
> Von: jmeter-user-return-30951-Matthias.Leis=sid.sachsen.de@
> jakarta.apache.org [mailto:jmeter-user-return-30951-Matthias.Leis=
> sid.sachsen.de@jakarta.apache.org] Im Auftrag von Thibaut Raballand
> Gesendet: Montag, 2. August 2010 23:49
> An: JMeter Users List
> Betreff: Re: jmeter and webflow: How to get another execution-Parameter for
> every single thread
>
> Hi,
>
> Your 302 redirects always on same page, or is it dynamic ?
> So that you just have to exact the url from it... as usual ?
>
> Tibo
>
> On Mon, Aug 2, 2010 at 18:46, Deepak Shetty <sh...@gmail.com> wrote:
>
> > hi
> > is this the first step? Do you have a cookie manager? Do you have follow
> > redirects instead of redirect automatically?
> >
> > If not it sounds like your application has a bug that doesnt allow it to
> > work under concurrent access. You can experiment with different (> 1
> second
> > diff between threads) ramp up times and see (if it starts working
> correctly
> > then it probably is a problem with your app)
> >
> > regards
> > deepak
> >
> >
> >
> >
> > On Mon, Aug 2, 2010 at 7:20 AM, Leis, Matthias - SID-NLKM <
> > Matthias.Leis@sid.sachsen.de> wrote:
> >
> > > Hi,
> > >
> > > I am currently testing a Spring Webflow Application. The URLs look like
> > > http://localhost:8080/spring/main-flow?execution=e1s1
> > > The initial request is http://localhost:8080/spring/main-flow, which
> > > responds with a HTTP Status Code 302 which redirects to
> > > http://localhost:8080/spring/main-flow?execution=e1s1.
> > > When I start my test with more than one thread, every thread gets the
> > > same URLs. So the application doesn't really execute anything (e.g.
> > > Database access) the second time the URL is called, but returns only
> the
> > > stored views (because the URL is always the same).
> > >
> > > The behaviour using a browser is different. The first instance gets
> > > http://localhost:8080/spring/main-flow?execution=e1s1, the second
> > > instance gets http://localhost:8080/spring/main-flow?execution=e2s1
> > > (notice e2s1 instead of e1s1) and so on and the application really
> > > executes database accesses, web service calls and so on.
> > >
> > > So my question is: Does anybody have an idea, how to achieve, that the
> > > first thread gets e1s1, the second thread e2s1 and so on.
> > >
> > > Thanks, any help is appreciated!
> > >
> > > Regards,
> > >
> > > Matthias
> > >
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
AW: jmeter and webflow: How to get another execution-Parameter for every single thread
Posted by "Leis, Matthias - SID-NLKM" <Ma...@sid.sachsen.de>.
Hi Deepak,
Yes, I have a Cookie Manager and follow redirects.
Setting a ramp time doesn't make a difference.
>hi
>is this the first step? Do you have a cookie manager? Do you have follow
>redirects instead of redirect automatically?
>
>If not it sounds like your application has a bug that doesnt allow it to
>work under concurrent access. You can experiment with different (> 1 second
>diff between threads) ramp up times and see (if it starts working correctly
>then it probably is a problem with your app)
>
>regards
>deepak
Hi,
The 302 always redirects from one execution-parameter to another. It's the only thing, that changes in the URL. But yes, it's always the same. Startpage: e1s1, first click: e2s1 and so on. So for my testplan, it's rather static.
>Hi Tibo,
>
>Your 302 redirects always on same page, or is it dynamic ?
>So that you just have to exact the url from it... as usual ?
>
>Tibo
The general problem is, that after the intial call of the application per http://localhost:8080/spring/main-flow
The application has to redirect me to http://localhost:8080/spring/main-flow?execution=e1s1. I can't just call this URL myself, because the application "doesn't know me" yet. But every thread gets the same redirect.
Regards
Matthias
-----Ursprüngliche Nachricht-----
Von: jmeter-user-return-30951-Matthias.Leis=sid.sachsen.de@jakarta.apache.org [mailto:jmeter-user-return-30951-Matthias.Leis=sid.sachsen.de@jakarta.apache.org] Im Auftrag von Thibaut Raballand
Gesendet: Montag, 2. August 2010 23:49
An: JMeter Users List
Betreff: Re: jmeter and webflow: How to get another execution-Parameter for every single thread
Hi,
Your 302 redirects always on same page, or is it dynamic ?
So that you just have to exact the url from it... as usual ?
Tibo
On Mon, Aug 2, 2010 at 18:46, Deepak Shetty <sh...@gmail.com> wrote:
> hi
> is this the first step? Do you have a cookie manager? Do you have follow
> redirects instead of redirect automatically?
>
> If not it sounds like your application has a bug that doesnt allow it to
> work under concurrent access. You can experiment with different (> 1 second
> diff between threads) ramp up times and see (if it starts working correctly
> then it probably is a problem with your app)
>
> regards
> deepak
>
>
>
>
> On Mon, Aug 2, 2010 at 7:20 AM, Leis, Matthias - SID-NLKM <
> Matthias.Leis@sid.sachsen.de> wrote:
>
> > Hi,
> >
> > I am currently testing a Spring Webflow Application. The URLs look like
> > http://localhost:8080/spring/main-flow?execution=e1s1
> > The initial request is http://localhost:8080/spring/main-flow, which
> > responds with a HTTP Status Code 302 which redirects to
> > http://localhost:8080/spring/main-flow?execution=e1s1.
> > When I start my test with more than one thread, every thread gets the
> > same URLs. So the application doesn't really execute anything (e.g.
> > Database access) the second time the URL is called, but returns only the
> > stored views (because the URL is always the same).
> >
> > The behaviour using a browser is different. The first instance gets
> > http://localhost:8080/spring/main-flow?execution=e1s1, the second
> > instance gets http://localhost:8080/spring/main-flow?execution=e2s1
> > (notice e2s1 instead of e1s1) and so on and the application really
> > executes database accesses, web service calls and so on.
> >
> > So my question is: Does anybody have an idea, how to achieve, that the
> > first thread gets e1s1, the second thread e2s1 and so on.
> >
> > Thanks, any help is appreciated!
> >
> > Regards,
> >
> > Matthias
> >
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: jmeter and webflow: How to get another execution-Parameter for
every single thread
Posted by Thibaut Raballand <th...@gmail.com>.
Hi,
Your 302 redirects always on same page, or is it dynamic ?
So that you just have to exact the url from it... as usual ?
Tibo
On Mon, Aug 2, 2010 at 18:46, Deepak Shetty <sh...@gmail.com> wrote:
> hi
> is this the first step? Do you have a cookie manager? Do you have follow
> redirects instead of redirect automatically?
>
> If not it sounds like your application has a bug that doesnt allow it to
> work under concurrent access. You can experiment with different (> 1 second
> diff between threads) ramp up times and see (if it starts working correctly
> then it probably is a problem with your app)
>
> regards
> deepak
>
>
>
>
> On Mon, Aug 2, 2010 at 7:20 AM, Leis, Matthias - SID-NLKM <
> Matthias.Leis@sid.sachsen.de> wrote:
>
> > Hi,
> >
> > I am currently testing a Spring Webflow Application. The URLs look like
> > http://localhost:8080/spring/main-flow?execution=e1s1
> > The initial request is http://localhost:8080/spring/main-flow, which
> > responds with a HTTP Status Code 302 which redirects to
> > http://localhost:8080/spring/main-flow?execution=e1s1.
> > When I start my test with more than one thread, every thread gets the
> > same URLs. So the application doesn't really execute anything (e.g.
> > Database access) the second time the URL is called, but returns only the
> > stored views (because the URL is always the same).
> >
> > The behaviour using a browser is different. The first instance gets
> > http://localhost:8080/spring/main-flow?execution=e1s1, the second
> > instance gets http://localhost:8080/spring/main-flow?execution=e2s1
> > (notice e2s1 instead of e1s1) and so on and the application really
> > executes database accesses, web service calls and so on.
> >
> > So my question is: Does anybody have an idea, how to achieve, that the
> > first thread gets e1s1, the second thread e2s1 and so on.
> >
> > Thanks, any help is appreciated!
> >
> > Regards,
> >
> > Matthias
> >
> >
> >
>