https://bz.apache.org/bugzilla/show_bug.cgi?id=64400
--- Comment #5 from Alex Podelko <apode...@yahoo.com> --- Here is the machine info from JMeter log: 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: Version 5.3-SNAPSHOT d652f1c 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: java.version=1.8.0_251 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: java.vm.name=Java HotSpot(TM) 64-Bit Server VM 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: os.name=Windows Server 2012 R2 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: os.arch=amd64 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: os.version=6.3 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: file.encoding=Cp1252 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: java.awt.headless=null 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: Max memory =1073741824 2020-05-01 14:56:52,073 INFO o.a.j.JMeter: Available Processors =8 2020-05-01 14:56:52,089 INFO o.a.j.JMeter: Default Locale=English (EN) 2020-05-01 14:56:52,089 INFO o.a.j.JMeter: JMeter Locale=English (EN) 2020-05-01 14:56:52,089 INFO o.a.j.JMeter: JMeterHome=C:\apache-jmeter-5.3-SNAPSHOT 2020-05-01 14:56:52,089 INFO o.a.j.JMeter: user.dir =c:\JMeter_Scripts I haven't changed anything in recording settings, all should be default. It is not that it records everything in one transaction controllers - for transaction with different names it worked fine. Only transactions starting similarly got together - see '1m request...' and '200k request...' in the actual script attached. Another interesting issue is that it broke it into several different transaction controllers in other places and it doesn't looks like it is time-based (some short got broken and some long didn't). That it is another issue, just mentioning here. -- You are receiving this mail because: You are the assignee for the bug.
