Hi
After doing A LOT(100+) of recordings I can confirm that the HTTP proxy has
some really unpredictable behavior.
*
Sometimes recordings end up in different recording controllers than
originally specified(http proxy chosen recording controller says "using
recording controller")
*
Sometimes the proxy looses its settings
*
Sometimes the proxy looses its original settings and gets duplicate or
"random" settings instread, like 80808080 instead of 8080
I tried having only one thread and a recording controller in my plan, this
resulted that the http requests were sometimes where stored in the recording
controller and sometime in the thread.
I tried having only one thread, this resulted that some recorded http request
were droped.
Heres a link to my orignal test plan:
http://www.badongo.com/file/2481964
regards Nino
________________________________
Fra: Nino Wael [mailto:[EMAIL PROTECTED]
Sendt: fr 02-03-2007 11:46
Til: JMeter Users List; JMeter Users List
Emne: SV: JMeter HTTP proxy server: sometimes loses recording controller?
Ok, thanks alot:)
________________________________
Fra: sebb [mailto:[EMAIL PROTECTED]
Sendt: fr 02-03-2007 11:03
Til: JMeter Users List
Emne: Re: JMeter HTTP proxy server: sometimes loses recording controller?
On 02/03/07, Nino Wael <[EMAIL PROTECTED]> wrote:
> Ahh, this morning I also found out where the missing recording items went.
> This is something that points in the direction that you mention, that I might
> have fuddled with the test plan while recording. Although it looks like all
> missing recording went into the first recording controller attached to the
> thread.
>
> Im not sure what you mean by:
>
> "In the recordings which failed for you, did you open any of the recorded
> items?"
>
> I could'nt at the time open the recorded items because I could not find them.
While the proxy is running, if you select any of the existing recorded
samples and then continue recording, it can cause subsequent samples
to be written to the wrong place. The proxy seems to lose track of
where it is supposed to store the next sample.
Until the bug is fixed, it's best not to navigate around the tree
until you have stopped the proxy.
> Regards Nino
>
> ________________________________
>
> Fra: sebb [mailto:[EMAIL PROTECTED]
> Sendt: to 01-03-2007 18:55
> Til: JMeter Users List
> Emne: Re: JMeter HTTP proxy server: sometimes loses recording controller?
>
>
>
> There is a known problem with the proxy recorder - if you select a
> node in the tree whilst it is recording, the next sample will be
> written there.
>
> In the recordings which failed for you, did you open any of the recorded
> items?
>
> On 01/03/07, Nino Wael <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I've just recorded 15 scenarios. Test plan are like this:
> >
> > Test Plan
> > ---thread
> > ----scenario A
> > ----scenario B
> > ----scenario ...
> >
> > Workbench
> > --- HTTP proxy server
> > --- Gaussian Random timer
> >
> > And sometimes while recording the HTTP proxy loses which recording
> > controller I set it to record to, has anyone else experienced this?
> >
> > regards Nino
> >
> >
> > ---------------------------------------------------------------------
> > 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
