Summary: | Warning logged when Boundary Extractor doesn't find any match | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Felix Schumacher <felix.schumacher> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | minor | Keywords: | FixedInTrunk |
Priority: | P2 | ||
Version: | Nightly (Please specify date) | ||
Target Milestone: | JMETER_5.5 | ||
Hardware: | All | ||
OS: | All | ||
Attachments: | Check for empty list |
@Nikola, could you test the next nightly or build from trunk? commit c054d3a4d329c02e305fdfb0818f682834130d8f AuthorDate: Thu Jun 3 18:04:18 2021 +0200 Warning logged when Boundary Extractor doesn't find any match Bugzilla Id: 65352 --- .../src/main/java/org/apache/jmeter/extractor/BoundaryExtractor.java | 3 +++ xdocs/changes.xml | 1 + 2 files changed, 4 insertions(+) Hi Felix, I checked Boundary Extractor behavior and it is fixed, no more WARN message in logs. Thank you. Jmeter 5.5 093df18 Microsoft Windows 10 Enterprise 64-bit java version "15.0.1" 2020-10-20 This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5545 |
Created attachment 37888 [details] Check for empty list When no match is found by the Boundary Extractor it will log a warning. All other extractors ignore that condition silently. Apart from this, throwing an exception is bad for performance. The fix will check if the list of matches is empty, before trying to save the elements of that list.