jgaalen

I'd like to reopen this ticket. It is a great addition. By far in most cases you want the sampler to fail if the regex extraction fails. Adding a response...

> Extractors are not the place to fail a sampler. Their job is strictly to extract. Assertions are the correct place for failing a sampler. Please re-close this ticket. It...

I'd like to bump this ticket. I simply don't agree with the statement that Extractors are not the place to fail a sampler. You have to think of a way...

[PR here](https://github.com/apache/jmeter/pull/6256)

> Have you considered adding test case for the feature? Not really, I'm not really into this. I've tried to make something out of an earlier existing (working) code for...

I made a heapdump and looked at it. It seems that the responseData is filled up for the transactionSampleResult.subResults. Somehow the transactionSampler needs to be cleared right after the data...

> > It would be incredibly more efficient to be able to store a single metric per requests, which holds all the data such as the data sent, received, status...

> Hey [@jgaalen](https://github.com/jgaalen), > > Thanks for your detailed explanation, that makes more sense now. > > However, I think what you're suggesting, which is basically having multiple values (not...

> > imagine how much network, storage, cpu and memory is saved, as well as speed up queries if you can combine values > > There's always a compromise, and...

I've done some more testing on this. It doesn't turn into a non-HTTP error against every server so I have no idea why that happens with one server I'm using,...