In that case the only possibility is that the RE is wrong.
Is it possible that there is trailing/leading white-space in the RE
field? This might cause a match failure.
BTW, for testing REs, the Java Request can be useful - just put some
sample text in the ResultData field (this will be the Body of the
response).
On 21/10/2008, sudheer reddy <[EMAIL PROTECTED]> wrote:
> *Body*
>
>
> On Tue, Oct 21, 2008 at 10:17 PM, sebb <[EMAIL PROTECTED]> wrote:
>
> > And which "Response Field to check" is selected?
> >
> > On 21/10/2008, sudheer reddy <[EMAIL PROTECTED]> wrote:
> > > Sebb
> > >
> > > yes you are right it is JDBC request only.
> > >
> > > I have used Regular expression extractor PP
> > >
> > > as a child to JDBC request.
> > >
> > > rgds
> > > Sudheer
> > >
> > >
> > > On Tue, Oct 21, 2008 at 9:59 PM, sebb <[EMAIL PROTECTED]> wrote:
> > >
> > > > On 21/10/2008, sudheer reddy <[EMAIL PROTECTED]> wrote:
> > > > > How to use JDBC request defaults in other requests
> > > >
> > > > There is no such element as a JDBC Request Default.
> > > >
> > > > There is a JDBC Connection Configuration element which can only be
> > > > used in a JDBC Request sampler.
> > > >
> > > > > I have written a sql query in JDBC request and I got the result but
> > i
> > > > don't
> > > > > know how to use this variable in other HTTP request.
> > > > >
> > > > > scenario
> > > > >
> > > > > using JDBC request i have got result which is assigned to a
> > variable say
> > > > '*
> > > > > A'.*
> > > > > **
> > > > > Now I have to use this '*A' *in HTTP request for a parameter say '
> > *X* '
> > > > .
> > > > >
> > > > > I have associated a Regular expression extractor to this JDBC
> > request
> > > > and
> > > >
> > > > What do you mean by "associated" ?
> > > >
> > > > > given values in this post processor as given below
> > > > >
> > > > > *reference name : variable*
> > > > > *regular expression : (.*)"*
> > > > > *template : $1$*
> > > > > *match number : 1*
> > > > > *default value : error*
> > > >
> > > > Looks OK.
> > > >
> > > > > **
> > > > > *here reference name and the variable name in JDBC request is same*
> > > > > **
> > > >
> > > > JMeter variables are not related in any way to SQL names.
> > > >
> > > > > and in HTTP request for a parameter
> > > > >
> > > > > *number : ${variable}*
> > > >
> > > > OK
> > > >
> > > > > **
> > > > > when i run the test and check the response data this parameter in
> > HTTP
> > > > > request is taking default value of regular expression instead of
> > JDBC
> > > > > variable.
> > > >
> > > > That means the RE PostProcessor has been run OK, and the HTTP sampler
> > > > used the correct variable, but the RE PP was either applied to the
> > > > wrong input or the RE was incorrect. Given that the RE is very simple,
> > > > it's probably because the RE PP was applied to the wrong input.
> > > >
> > > > Did you add the RE PP as a child of the JDBC Sampler?
> > > >
> > > > > Assist me in solving ths issue
> > > > >
> > > > > rgds
> > > > > Sudheer
> > > > > **
> > > > >
> > > >
> > >
> > > > ---------------------------------------------------------------------
> > > > 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]
