https://bz.apache.org/bugzilla/show_bug.cgi?id=64400
Felix Schumacher <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #12 from Felix Schumacher <[email protected]> --- (In reply to Alex Podelko from comment #11) > Your recording looks fine indeed. It does, as I let enough time pass between changing the name of the transaction and recording the next samples. > > As you may see from attached 'the script illustrating the issue', I > reproduced the same problem with a very short script recorded with Google > search (so it shouldn't be related to my specific system). 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. > > It was just standard recording - I type in a transaction name into pop up > window (I actually am not aware about any other methods), click on > something, wait until it finishes, change the name for the next transaction. > Nothing quick - some transaction takes more than a minute and I am not a > quick typist. Clicking some actions may invoke some requests in parallel in > the background - but it is the only concurrency I can think about. > > The only interesting specific of my environment is that I am doing it on a > server (VM) with 8 CPUs... Not sure how it may be connected, but sometimes > it creates really amusing effects. > > One more thing comes to mind that I haven't replaced the whole name - just > changed the ending of the transaction... Can you try out the patch I attached? If not, I would submit it to trunk and you could try out next nightly. > > Thanks, > Alex -- You are receiving this mail because: You are the assignee for the bug.
