On 05/06/07, Thomson, Alex <[EMAIL PROTECTED]> wrote:
Hi,

I am trying to use the ${__threadNum} function to send different files
for each user in an HTTP POST, however it is very difficult to see what
file path was actually sent by JMeter.

e.g. 900 users, 0 ramp up & 1 loop.

That's a very high initial load; with 1 loop it's likely that startup
overhead will be a large proportion of the sample times...

HTTP Request HttpClient POST with
file name = /path/example/file_${__threadNum}.txt

From that I presume each user will send a separate file referenced by
the thread number.

Yes.

I am duplicating the function call in the HTTP Request HttpClient Name
so that I can at least see the number returned by the function for each
sample. E.g. HTTP POST ${__threadNum}

OK

Is there any way to log what file was actually sent with the POST? I
can't tell whether there is an issue with the system under test or the
jmeter configuration.

Does the filename appear in the Tree View Listener?
Try it with 2 or 3 threads, and remove for the main testing.

You could use the __log function:

${__log(/path/example/file_${__threadNum}.txt)}


Regards,

Alex
This email message and any attachments thereto are intended only for use by the 
addressee(s) named above, and may contain legally privileged and/or 
confidential information. If the reader of this message is not the intended 
recipient, or the employee or agent responsible to deliver it to the intended 
recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received this 
communication in error, please immediately notify the [EMAIL PROTECTED] and 
destroy the original message.

Please consider the environment before printing this email.

NDS Limited   Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom
A company registered in England and Wales   Registered no. 3080780    VAT no. 
GB 603 8808 40-00


---------------------------------------------------------------------
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