You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2004/01/12 15:35:08 UTC
DO NOT REPLY [Bug 26058] New: -
CSVRead works with unique file only, no two files
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26058>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26058
CSVRead works with unique file only, no two files
Summary: CSVRead works with unique file only, no two files
Product: JMeter
Version: 1.9.1
Platform: All
OS/Version: Other
Status: NEW
Severity: Blocker
Priority: Other
Component: Main
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: Joerg-Cyril.Hoehle@t-systems.com
The doc says "a single instance of the file is opened and used for all threads".
What JMeter does is return values from a single CSV file, even when the filename
argument differs. I.e. it does not obey the filename argument, but continues to
read from whatever file was first accessed in the test script.
${__CSVRead(${myfilename},0)
${__CSVRead(${otherfilename},0) -> values from file $myfilename, $otherfilename
is completely ignored
Given the reference to StringFromFile, which says that the same file may be
opened multiple times by JMeter, I understood that the above phrase would refer
to some resource pool and that the file descriptor would be shared by all
threads. This is quite different. I did not interpret it as meaning that CSVRead
would only allow a single file to be read from, across a whole complex test
case. I believe this to be a bug, since it causes unreliable and
unforeseen behaviour
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org