Bug 40804 - Counter default behavior is not to count at all
Counter default behavior is not to count at all
Status: RESOLVED FIXED
Product: JMeter
Classification: Unclassified
Component: Main
2.2
Other other
: P2 normal with 1 vote (vote)
: ---
Assigned To: JMeter issues mailing list
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2006-10-20 08:11 UTC by Rub
Modified: 2006-11-27 14:47 UTC (History)
0 users



Attachments
if max value is left blank it assumes Long.MAX_VALUE and not zero (819 bytes, patch)
2006-10-20 08:17 UTC, Rub
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Rub 2006-10-20 08:11:01 UTC
The initial behaviour of the Counter Pre-processor is rather counterintuitive.
If you don't set a maximum it will interpret that the maximum is zero and
therefore will always return the same value.  I think the default value when the
user leave the max field blank should be Long.MAX_VALUE.
Comment 1 Rub 2006-10-20 08:17:28 UTC
Created attachment 19035 [details]
if max value is left blank it assumes Long.MAX_VALUE and not zero

Changes the actual behavior of the Counter that is very counterintutive -> If
left blank Max become 0 so it never increments. With this patch if it left
blank it assumes you meant Long.MAX_VALUE so the default behavior is that the
counter actually counts.
Comment 2 Sebb 2006-11-27 14:47:59 UTC
Thanks; code has been updated in SVN and will be in the next nightly (and in 2.2.1)