But that does not explain why you are seeing ${smtpaddress} in the
POST rather than the contents of the variable "smtpaddress" - are you
sure that the variable is defined at the point of use?

e.g. Add a Debug Sampler just before the POST sampler.

On 28/11/2008, Adam Schieman <[EMAIL PROTECTED]> wrote:
>
>  Great tip! The variables seem to be read, but they are garbled with
>  "box" characters in between each letter.
>
>
>
>  -----Original Message-----
>  From: sebb [mailto:[EMAIL PROTECTED]
>  Sent: Friday, November 28, 2008 5:21 AM
>  To: JMeter Users List
>  Subject: Re: CSV data set and HTTP request variables
>
>  Try adding a Debug Sampler and View Results Tree Listener to show the
>  variables.
>
>  On 27/11/2008, Fitzpatrick, Adrian <[EMAIL PROTECTED]> wrote:
>  >
>  >  Hi,
>  >
>  >  Everything you have described sounds correct to me and I dont think
>  you are
>  >  missing anything. The order shouldnt matter either. Perhaps JMeter
>  isnt
>  >  picking up your CSV file properly. Maybe check jmeter.log in the
>  JMeter bin
>  >  directory and see if there is any more info there?
>  >
>  >  - Adrian
>  >
>  >  ************************
>  >
>  >  This message has been delivered to the Internet by the Revenue
>  Internet e-mail service (OP)
>  >
>  >  *************************
>  >
>  >  ---------------------------------------------------------------------
>  >  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]
>
>
>
> ---------------------------------------------------------------------
>  This transmission (including any attachments) may contain confidential 
> information, privileged material (including material protected by the 
> solicitor-client or other applicable privileges), or constitute non-public 
> information. Any use of this information by anyone other than the intended 
> recipient is prohibited. If you have received this transmission in error, 
> please immediately reply to the sender and delete this information from your 
> system. Use, dissemination, distribution, or reproduction of this 
> transmission by unintended recipients is not authorized and may be unlawful.
>
>
> ---------------------------------------------------------------------
>  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