OK, thanks for confirming the work-round is OK. ==
The next version of JMeter will have a way of specifying an idle timeout in case the server does not send the optional header (Keep-Alive) The HC4 stale connection check is currently a bit expensive, as it applies to every sample. That is why the default was changed to disable it. It may be possible to add a cheaper stale check (e.g. every n samples, or if the connection has been idle for a while). On 7 March 2014 11:32, Guruprasad R <[email protected]> wrote: > Thanks sebb.. that was helpful.. It works fine after i made the changes > pointed out by you. > > Regards, > Guru > > On Fri, Mar 7, 2014 at 4:28 PM, sebb <[email protected]> wrote: > >> On 7 March 2014 08:38, Guruprasad R <[email protected]> wrote: >> > Hi all, i am sending a http request from jmeter-2.9 and jmeter-2.11. >> > Jmeter-2.11 shows exception in response for alternate requests. The >> script >> > works well in jmeter-2.9 without any issues. >> >> This looks like an example of >> >> https://issues.apache.org/bugzilla/show_bug.cgi?id=56119 >> >> See comment 14 for a work-round. >> >> Alternatively deselect Keep-Alive on the previous sample to the same host. >> >> The problem is likely to be idle connection timeout, which was >> previously masked by >> > I placed a breakpoint in my server to see whether the alternate requests >> > are reaching my server. But its not reaching the server at all. >> >> It's not reaching as far as logging the request. >> >> <snip/> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
