[
https://issues.apache.org/jira/browse/CXF-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CXF-6912.
-------------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
3.1.7
3.0.10
commit fix
http://git-wip-us.apache.org/repos/asf/cxf/commit/501922f3 for master
http://git-wip-us.apache.org/repos/asf/cxf/commit/e989d4fa for 3.1.x-fixes
branch
http://git-wip-us.apache.org/repos/asf/cxf/commit/ea76c196 for 3.0.x-fixes
branch
> introduce CONNECTION_MAX_IDLE property for AHC
> ----------------------------------------------
>
> Key: CXF-6912
> URL: https://issues.apache.org/jira/browse/CXF-6912
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 3.0.10, 3.1.7, 3.2.0
>
>
> currently we have the CONNECTION_TTL property for AHC, this is used to
> specify a connection TimeToLive, no matter the connection is active or not.
> For some scenarios, users wanna specify the value for how long an idle
> connection should exist in the connection pool, if reach that timespan, just
> close the idle connection.
> We need introduce another property named CONNECTION_MAX_IDLE to do it. To let
> CONNECTION_MAX_IDLE take effect, customer need configure CONNECTION_TTL as
> "0" which means the connection does not have an expiry deadline and use the
> CONNECTION_MAX_IDLE to close the idle connection only, so that the actively
> used connection could be still reused by the connection pool
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
