I don't understand the use-case or why anyone would want to include any timeouts in the response times if they're added by anything else other than the system under test. The purpose of the tool is to measure server side response times (from just before starting a new connection to the point just after receiving the last bit of the response), not the measurement tool's own processing/time-wait periods.
That been said, I've seen use-cases where one might need to calculate the total duration of an action that requires multiple/nested requests and in order to get the total value for this group, one can use the transaction controller and adding a listener that has this controller in its scope. I think it might have some options that might prove useful: http://jmeter.apache.org/usermanual/component_reference.html#Transaction_Controller I must insist though that a bigger problem would be the requirements and making sure they are justified. Cheers, A On Tue, Aug 16, 2016 at 3:11 PM, Sankar Das <[email protected]> wrote: > Hi, > > *Scenario*: My requirement is to do some actions when the assertion fails. > > *Issue*:When the thread is timing out (have provided the timeout details > in" HTTP Request Defaults", JMeter "Duration Assertion" is not calculating > the timing of the timed out sampler. > > Hence not able to do the action. > > *Expected*. > Response duration should be able to calculate the timeout time of the > sampler ,even if the sampler is timed-out. >
