On 10/08/07, Lenin Basheer <[EMAIL PROTECTED]> wrote:
>
> Thanks Sebb. That worked. I use the ${__P(property1,n7043)} as though a 
> variable now.
> However ${__P(property1)} returns a 1 . Is this the expected behaviour ??

Yes - if the property "property1" is not defined, then the __P()
function returns 1, see:

http://jakarta.apache.org/jmeter/usermanual/functions.html#__P

> If so , will a setproperty() work if i intend to change the "property1" some 
> time later in the test plan ??
>

The only way to change a property is to use the __setProperty() function:

http://jakarta.apache.org/jmeter/usermanual/functions.html#__setProperty


>
>
>
> sebb <[EMAIL PROTECTED]>
>
> 08/09/2007 05:03 PM
>
> Please respond to
> "JMeter Users List" <[email protected]>
>
>
> To"JMeter Users List" <[email protected]>
>
> cc
>
> SubjectRe: Jmeter to stimulate Failover mechanism
>
>
>
>
>
>
>
>
> Properties are not the same as variables, i.e. you cannot use
> ${property}, you need to use ${__P(property)}.
>
> On 08/08/07, Lenin Basheer <[EMAIL PROTECTED]> wrote:
> >
> > Hi All,
> >
> > I was able to proceed a bit further in stimulating a fail over mechanism.
> > For this , I set the server ip and port as two separate properties using the
> > _P() method.
> > And i intend to reset the properties as part of a bean shell script with the
> > help of a bean shell assertion.
> >
> > however i am not able to use the property variables (serverip and port ) as
> > standard Jmeter variables, ${serverip} and ${serverport} else where in the
> > test plan
> > I initialize the property as part of the user defined variables in the Test
> > Plan component.
> >
> > like,
> > host        ${__P(serverip,n7043)}
> > port        ${__P(serverport,7001)}
> >
> > please can some one shed some light on this.
> >
> > many thanks,
> > Lenin
> >
> >
> >
> > ----- Forwarded by Lenin Basheer/IBS on 08/08/2007 08:24 PM -----
> >
> >
> > Hi All,
> >
> > I am trying to use Jmeter to stimulate a failover mechanism where in during
> > the test the server the test connects to fails and the requests get routed
> > to the secondary server.
> >
> > Heres how my plan looks like.
> >
> > Test Plan         -
> >                -        Http Request Defaults
> >                -        Http Cookie Manager
> >                -         Thread Group
> >                        -        User Parameter(s)
> >                        -        Random Order Controller
> >                        -                                -- Throughput
> > controller(s)
> >
> > How will  it be possible to stimulate a fail over scenario with the above
> > test plan ? I expect the url to be modified by some criteria , say the first
> > server response being a failrure.
> >
> > Thanks and regards,
> > Lenin
> >
> >
> >
> > DISCLAIMER:
> >
> > "The information in this e-mail and any attachment is intended only for the
> > person to whom it is addressed and may contain confidential and/or
> > privileged material. If you have received this e-mail in error, kindly
> > contact the sender and destroy all copies of the original communication. IBS
> > makes no warranty, express or implied, nor guarantees the accuracy, adequacy
> > or completeness of the information contained in this email or any attachment
> > and is not liable for any errors, defects, omissions, viruses or for
> > resultant loss or damage, if any, direct or indirect."
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> >
> >
> >
> >
> > DISCLAIMER:
> >
> > "The information in this e-mail and any attachment is intended only for the
> > person to whom it is addressed and may contain confidential and/or
> > privileged material. If you have received this e-mail in error, kindly
> > contact the sender and destroy all copies of the original communication. IBS
> > makes no warranty, express or implied, nor guarantees the accuracy, adequacy
> > or completeness of the information contained in this email or any attachment
> > and is not liable for any errors, defects, omissions, viruses or for
> > resultant loss or damage, if any, direct or indirect."
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
>
>
>
>
>
> DISCLAIMER:
>
> "The information in this e-mail and any attachment is intended only for the 
> person to whom it is addressed and may contain confidential and/or privileged 
> material. If you have received this e-mail in error, kindly contact the 
> sender and destroy all copies of the original communication. IBS makes no 
> warranty, express or implied, nor guarantees the accuracy, adequacy or 
> completeness of the information contained in this email or any attachment and 
> is not liable for any errors, defects, omissions, viruses or for resultant 
> loss or damage, if any, direct or indirect."
>
>
>
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to