https://bz.apache.org/bugzilla/show_bug.cgi?id=64400
Alex Podelko <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW --- Comment #13 from Alex Podelko <[email protected]> --- >The problem can be seen, when you record samples shortly after changing the >>transaction name. JMeter doesn't take the name of the transaction into >account, >when it decides if it should create a new controller. I only looks >at the time of >the last sample. >The default gap time seems to be 5 seconds. Hmm... Didn't realized that... Well, then it may be working here as designed. I indeed may record the google script faster than 5 sec - if I wait longer, it put requests into different transactions. With my product, it is more interesting. When a 'request' (think a 'form' here) is open, it polls the server each 4 seconds. So it never could be a case when we have 5+ sec between HTTP requests - so they all got into one transaction controller. Then the more interesting question would be how '200k request *' got broken into multiple transaction controllers - when we still have /epm/ui-rest/v1/changeEvents invoked every 4 sec. [Another question is why would we break it by time if we specify transaction names - if somebody cares to specify transaction names, I can't come with the case why he may be interested to break it not according to specified name. Any thoughts?] -- You are receiving this mail because: You are the assignee for the bug.
