[
https://issues.apache.org/jira/browse/HTTPCLIENT-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913237#action_12913237
]
Michajlo Matijkiw commented on HTTPCLIENT-1000:
-----------------------------------------------
Yes, the current constructors still exist, and if the TTL argument is not
provided than it will be set to -1, representing "forever."
> Configure Maximum Connection Lifetimes
> --------------------------------------
>
> Key: HTTPCLIENT-1000
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1000
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Reporter: Michajlo Matijkiw
>
> Provide a means of configuring a maximum lifetime for HttpClient connections.
> Currently, it would appear as long as a connection is used it may persist
> indefinitely.
> This would be useful for situations where HttpClient needs to react to DNS
> changes, such as the following situation that may occur when using DNS load
> balancing:
> - HttpClient maintains connections to example.com which resolves to IP A
> - Machine at IP A fails, and example.com now resolves to backup machine at
> IP B
> - Since IP A is failing, connections are destroyed, and new connections are
> made to IP B
> - Machine at IP A recovers, but HttpClient maintains connections to IP B
> since the connections are still healthy
> The desired behavior would be that connections to IP B will reach their
> connection lifetime, and new connections could be created back to IP A
> according to the updated DNS settings.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
