https://issues.apache.org/bugzilla/show_bug.cgi?id=56119
--- Comment #18 from Sebb <[email protected]> --- On the face of it, I don't think it is a bug - perhaps an enhancement request. I'm not sure I fully understand how the timer interacts with the staleCheck setting, unless there is some S3 setting that disallows long-lasting sessions? I think further tests are needed to establish exactly how enabling the staleCheck prevents the problem. It would be interesting to know if disabling keep-alive solved the issue in the absence of staleCheck. Ideally we need a test server (either public or easy to set up locally) that shows the same behaviour as being reported here. JMeter already supports closing a connection, i.e. forcing the next sample to use a new connection. It looks like the problem may be that the connection is expiring somehow. If this is indeed the case, then there might be a need to provide automated connection closing based on re-use count and/or idle time. But first we need to know if that is really what the problem is. -- You are receiving this mail because: You are the assignee for the bug.
