https://issues.apache.org/bugzilla/show_bug.cgi?id=55325
--- Comment #9 from Sebb <[email protected]> --- I don't think a changed clock could affect more than a few samples, because the time is refetched per sample. Unless all the negative samples started before the clock was reset, which seems unlikely as the negative times started at 04:28:17 and lasted until the end at 04:31:31. But there is another oddity in the elapsed times - they seem to get bigger and bigger, starting at 40308 and reaching 755182 just before the negative times start. That's a ratio of about 15:1 which is very strange. It might just possibly be worth trying disabling the nano-second time resolution by setting the JMeter property: sampleresult.useNanoTime=false I suppose if the nano-second clock is very badly behaved it might cause some issues, but I'm not sure how the negative times can come about. -- You are receiving this mail because: You are the assignee for the bug.
