Ahh, so sorry, your additional comments were further down in the post,
I only saw the
.* is greedy, and probably not what you want - it will look for the
last possible PARM after /details/myServerProcess
Use .*? or .+? instead.
lines - I will look, thanks!
On 8/14/06, sebb <[EMAIL PROTECTED]> wrote:
On 14/08/06, Michel Plungjan <[EMAIL PROTECTED]> wrote:
> But it does work - looks more like some glitch is happening when under
> pressure - I just want to rule out that it is a glitch at the server
> side
That's why I suggested saving the responses.
> Run1 output URLs:
>
> details/myServerProcess?NR=1500038&PARM=${KK}&.....
> details/myServerProcess?NR=1500039&PARM=O1&.....
> details/myServerProcess?NR=1500040&PARM=P1&.....
> details/myServerProcess?NR=1500041&PARM=Z1&.....
>
> Run2 output URLs:
>
> details/myServerProcess?NR=1500038&PARM=X1&.....
> details/myServerProcess?NR=1500039&PARM=O1&.....
> details/myServerProcess?NR=1500040&PARM=P1&.....
> details/myServerProcess?NR=1500041&PARM=${KK}&.....
>
> No change in between runs so unless the server returned two different
> urls (not super likely but very hard to verify unless I find a way to
> let JMeter tell me the inputt string) I do not see why this happens
>
I already explained how to save the responses, which are the input for the RE.
> Thanks for looking
>
> On 8/14/06, sebb <[EMAIL PROTECTED]> wrote:
> > On 14/08/06, Michel Plungjan <[EMAIL PROTECTED]> wrote:
> > > Hi, I have a Regular Expression Extractor
> > >
> > > /details/myServerProcess.*PARM=(.+?)&
> >
> > .* is greedy, and probably not what you want - it will look for the
> > last possible PARM after /details/myServerProcess
> >
> > Use .*? or .+? instead.
> >
> > >
> > > Template $1$
> >
> > What are the other settings?
> >
> > > and a ForEach controller
> > > using
> > >
> > > output variable name: KK
> > >
> > > Using a counter, I run searches that gives results like these
> > > counter = 00000005:
> > > <a href="/details/myServerProcess?....&NUMBER=00000005&PARM=P1&.....
> > >
> > > next counter: counter = 00000006:
> > > <a href="/details/myServerProcess?....&NUMBER=00000006&PARM=X2&.....
> > >
> > > and so on
> > >
> > > I know the counter number and need to add the KK extracted by the
> > > regexp to do another http request
> > >
> > > This works in most cases, but when I ramp up, I get the occational
> > >
> > > ${KK}
> > > instead of for example X2
> > >
> > > in my combined url.
> >
> > This means that the variable KK is not defined, possibly because the
> > RE did not match. I suggest you provide a default value for the RE.
> >
> > > I have tested that for the number given, I do get a PARM when using a
> > > browser so it seems to be random.
> > >
> > > How can I see the line processed and the result found in a report?
> > > i.e. I would like to see a file that shows
> > > <a href="/details/myServerProcess?....&NUMBER=00000005&PARM=P1&..... -
> > > extracted P1
> > >
> > > or similar
> >
> > You can save the input data using the Save Responses to a file
Post-Processor.
> >
> > You can log the values of variables using a Java Request sampler with
> > an attached child listener.
> >
> > > Thanks
> > >
> > > Michel
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
