Summary: | FileServer should provide thread-safe parsing | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Sebb <sebb> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Bug Depends on: | |||
Bug Blocks: | 53807 |
Description
Sebb
2012-08-31 13:21:15 UTC
Just realised that it won't work as orginally envisaged - there needs to be a lock to ensure that only a single thread can read multiple consecutive lines. The functionality is still needed, but will need to be provided some other way, for example via a callback mechanism. Details TBA. One way round this is to provide access to the reader, but require the caller to synchronise on the FileServer instance. This is not ideal, as it means locking is not totally controlled by the FileServer class. URL: http://svn.apache.org/viewvc?rev=1384590&view=rev Log: FileServer should provide direct access to the BufferedReader Bugzilla Id: 53806 Modified: jmeter/trunk/src/core/org/apache/jmeter/services/FileServer.java jmeter/trunk/xdocs/changes.xml Rather than provide access to the buffered reader, it would be easier to control synchronisation if FileServer provided the data as a CSV parsed String array. URL: http://svn.apache.org/viewvc?rev=1386736&view=rev Log: FileServer should provide thread-safe parsing Bugzilla Id: 53806 Modified: jmeter/trunk/src/components/org/apache/jmeter/config/CSVDataSet.java jmeter/trunk/src/core/org/apache/jmeter/services/FileServer.java jmeter/trunk/xdocs/changes.xml This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2908 |