| Summary: | ForEach Controller (empty collection processing error) | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | Dmitry Kudrenko <dmitry> |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 2.3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | other | ||
(In reply to comment #0) > If ForEach Controller used in the cycle and input collection is empty at the > first n iterations and not empty starting from the n+1 iteration then ForEach > starts to process collections from n+1 element. > > Example > Short plan description: > Thread Group > -While (several times) > --HTTP Request > ---RegExp Extractor (receives collection ‘input’) > --ForEach (input:out) > ---HTTP Request using out value > > First iteration: input is empty > Second iteration: input {element1, element2, element3} > For each will process started from element2. Seems the problem in the org.apache.jmeter.control.ForeachController.next() method. As I understand, It should reset loop counter if collection is empty. public Sampler next() { if (emptyList()) { reInitialize(); + resetLoopCount(); return null; } return super.next(); } Thanks very much for the report and the patch. I can confirm the problem, and the patch fixes it - good work. Applied to SVN in r588094 This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2039 |
If ForEach Controller used in the cycle and input collection is empty at the first n iterations and not empty starting from the n+1 iteration then ForEach starts to process collections from n+1 element. Example Short plan description: Thread Group -While (several times) --HTTP Request ---RegExp Extractor (receives collection ‘input’) --ForEach (input:out) ---HTTP Request using out value First iteration: input is empty Second iteration: input {element1, element2, element3} For each will process started from element2.