hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michajlo Matijkiw (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HTTPCLIENT-1000) Configure Maximum Connection Lifetimes
Date Tue, 21 Sep 2010 20:26:36 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michajlo Matijkiw updated HTTPCLIENT-1000:
------------------------------------------

    Description: 
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.

  was:
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 DNS changes, such as the
following:
 - 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.


> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message