Timestamp and/or elasped problem on downloads of included resources.

Hello,

I noticed in the csv result files in non-gui mode, a problem with the
timestamp and/or elasped (duration in ms) correspondence on the included
http resources.

With a simple jmeter script:
[image: image.png]
We see in the result tree that the start of requests and the transaction
are in the format HH:MM:SS and the duration in milliseconds. Everything
seems to be good. But when I run the same thing from command line:
[image: image.png]
The start of requests and the transaction are in 13-digit timestamp
(therefore with milliseconds) and the durations are also in milliseconds.
And this is where the problem arises:
[image: image.png]
I see the second query finishing after the end timestamp of the transaction
it is attached to. The same goes for the resources of this second request.
So question: Why? Isn't there a problem somewhere or I misunderstood? 2
Possibilities: Either there is a problem with the timestamps of requests
and resources, or there is a problem with the duration of the transaction
and this is even more serious.


The point of my question is that I am trying to use the non-gui results
(.csv) to match the http+resources request lines to the transaction lines
but for this I need the timestamp and elapsed of the http+resources
requests "enter" the period of transactions to which they are attached.

Any help on this topic will be welcome.

Please forgive my broken English, I am French.

Sincerely.

Emmanuel