[Red Hat JIRA] (MODCLUSTER-720) Allow mod_cluster listener to register at <Service> level rather than <Server> level
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/MODCLUSTER-720?page=com.atlassian.jira.p... ]
Radoslav Husar updated MODCLUSTER-720:
--------------------------------------
Fix Version/s: 1.4.4.Final
(was: 1.4.3.Final)
> Allow mod_cluster listener to register at <Service> level rather than <Server> level
> ------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-720
> URL: https://issues.redhat.com/browse/MODCLUSTER-720
> Project: mod_cluster
> Issue Type: Feature Request
> Components: Core & Container Integration (Java)
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 2.0.0.Alpha1, 1.4.4.Final
>
>
> The container even handler needs to handle sequence of events that are sent when the listener is on the <Service> level as opposed to only handling the chain of events on the <Server> level. The intention is to only register that service the listener is registered on thus a service stub that only filers that service is then passed around.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 9 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 closed MODCLUSTER-728.
-------------------------------------
> 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, 9 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:
--------------------------------------
Resolution: Done
Status: Resolved (was: Pull Request Sent)
Merged.
> 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, 10 months