[Red Hat JIRA] (MODCLUSTER-728) Proxy configured by a hostname caches resolved address indefinitely
by Ilia Vassilev (Jira)
[ https://issues.redhat.com/browse/MODCLUSTER-728?page=com.atlassian.jira.p... ]
Ilia Vassilev updated MODCLUSTER-728:
-------------------------------------
Labels: downstream_dependency (was: )
> Proxy configured by a hostname caches resolved address indefinitely
> -------------------------------------------------------------------
>
> Key: MODCLUSTER-728
> URL: https://issues.redhat.com/browse/MODCLUSTER-728
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.4.2.Final
> Reporter: Aaron Ogburn
> Assignee: Radoslav Husar
> Priority: Major
> Labels: downstream_dependency
> Fix For: 2.0.0.Alpha1, 1.4.3.Final
>
>
> With a proxy configured by host name, the InetSocketAddress is created once and reused so the host name is never resolved again. This may be an issue if the proxy host name resolution changed to a new ip address. If that happens, mod_cluster will never connect to the proxy on the new ip unless the JVM is restarted or the proxy is manually removed and added again.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (MODCLUSTER-728) Proxy configured by a hostname caches resolved address indefinitely
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/MODCLUSTER-728?page=com.atlassian.jira.p... ]
Radoslav Husar updated MODCLUSTER-728:
--------------------------------------
Summary: Proxy configured by a hostname caches resolved address indefinitely (was: Refresh ip of proxy)
> Proxy configured by a hostname caches resolved address indefinitely
> -------------------------------------------------------------------
>
> Key: MODCLUSTER-728
> URL: https://issues.redhat.com/browse/MODCLUSTER-728
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.4.2.Final
> Reporter: Aaron Ogburn
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 2.0.0.Alpha1, 1.4.3.Final
>
>
> With a proxy configured by host name, the InetSocketAddress is created once and reused so the host name is never resolved again. This may be an issue if the proxy host name resolution changed to a new ip address. If that happens, mod_cluster will never connect to the proxy on the new ip unless the JVM is restarted or the proxy is manually removed and added again.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (MODCLUSTER-728) Refresh ip of proxy
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/MODCLUSTER-728?page=com.atlassian.jira.p... ]
Radoslav Husar commented on MODCLUSTER-728:
-------------------------------------------
Reclassified as bug, opened a PR similar to Aaron's but no flag and avoids situations where proxy was configured as IP so no 'refresh' is possible. See https://github.com/modcluster/mod_cluster/pull/503
> Refresh ip of proxy
> -------------------
>
> Key: MODCLUSTER-728
> URL: https://issues.redhat.com/browse/MODCLUSTER-728
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.4.2.Final
> Reporter: Aaron Ogburn
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 2.0.0.Alpha1, 1.4.3.Final
>
>
> With a proxy configured by host name, the InetSocketAddress is created once and reused so the host name is never resolved again. This may be an issue if the proxy host name resolution changed to a new ip address. If that happens, mod_cluster will never connect to the proxy on the new ip unless the JVM is restarted or the proxy is manually removed and added again.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (MODCLUSTER-728) Refresh ip of proxy
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/MODCLUSTER-728?page=com.atlassian.jira.p... ]
Radoslav Husar updated MODCLUSTER-728:
--------------------------------------
Issue Type: Bug (was: Enhancement)
> Refresh ip of proxy
> -------------------
>
> Key: MODCLUSTER-728
> URL: https://issues.redhat.com/browse/MODCLUSTER-728
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.4.2.Final
> Reporter: Aaron Ogburn
> Assignee: Radoslav Husar
> Priority: Major
>
> With a proxy configured by host name, the InetSocketAddress is created once and reused so the host name is never resolved again. This may be an issue if the proxy host name resolution changed to a new ip address. If that happens, mod_cluster will never connect to the proxy on the new ip unless the JVM is restarted or the proxy is manually removed and added again.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (MODCLUSTER-728) Refresh ip of proxy
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/MODCLUSTER-728?page=com.atlassian.jira.p... ]
Radoslav Husar updated MODCLUSTER-728:
--------------------------------------
Fix Version/s: 2.0.0.Alpha1
1.4.3.Final
> Refresh ip of proxy
> -------------------
>
> Key: MODCLUSTER-728
> URL: https://issues.redhat.com/browse/MODCLUSTER-728
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.4.2.Final
> Reporter: Aaron Ogburn
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 2.0.0.Alpha1, 1.4.3.Final
>
>
> With a proxy configured by host name, the InetSocketAddress is created once and reused so the host name is never resolved again. This may be an issue if the proxy host name resolution changed to a new ip address. If that happens, mod_cluster will never connect to the proxy on the new ip unless the JVM is restarted or the proxy is manually removed and added again.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months