apr-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 63632] reslist kills all idle connections when acquiring a new one, not considering smax value
Date Tue, 27 Aug 2019 09:43:16 GMT

--- Comment #2 from Ruediger Pluem <rpluem@apache.org> ---
I would argue the other way round. The reslist_maintain code needs to be fixed.
The idea of the ttl parameter is to never ever hand out expired resources as
they could be stale (think of situation where you know that after a certain
period of inactivity a TCP connection will be dead). This is also documented in
the API:

* @param ttl If non-zero, sets the maximum amount of time in microseconds an
 *            unused resource is valid.  Any resource which has exceeded this
 *            time will be destroyed, either when encountered by
 *            apr_reslist_acquire() or during reslist maintenance.

But I agree that there is some inconsistency regarding the smax parameter.
Either we need to kill all resources above smax during each maintenance run or
we need to have an additional 'idle' parameter to determine after what time
everything above smax is destroyed.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail: bugs-unsubscribe@apr.apache.org
For additional commands, e-mail: bugs-help@apr.apache.org

View raw message