Bug 65352 - Warning logged when Boundary Extractor doesn't find any match
Summary: Warning logged when Boundary Extractor doesn't find any match
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: Nightly (Please specify date)
Hardware: All All
: P2 minor (vote)
Target Milestone: JMETER_5.5
Assignee: JMeter issues mailing list
Keywords: FixedInTrunk
Depends on:
Reported: 2021-06-03 16:05 UTC by Felix Schumacher
Modified: 2021-09-30 08:48 UTC (History)
0 users

Check for empty list (1.22 KB, patch)
2021-06-03 16:05 UTC, Felix Schumacher
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Schumacher 2021-06-03 16:05:01 UTC
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.
Comment 1 Felix Schumacher 2021-06-03 16:08:43 UTC
@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(+)
Comment 2 eR@SeR 2021-09-30 08:48:16 UTC
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
Comment 3 The ASF infrastructure team 2022-09-24 20:38:22 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5545