[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-49) mod_advertise sends (null) X-Manager-Address by default

[Michal Babacek (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek closed MODCLUSTER-49.
------------------------------------



Closing. Clean-up.
At least one of the following applies:

  * the issue has been thoroughly tested as a part of one of the current releases
or
  * it hasn't occurred in ~2 years
or
  * it's utterly harmless

> mod_advertise sends (null) X-Manager-Address by default
> -------------------------------------------------------
>
>                 Key: MODCLUSTER-49
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-49
>             Project: mod_cluster
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.Beta3
>            Reporter: Paul Ferraro
>            Assignee: Jean-Frederic Clere
>            Priority: Optional
>             Fix For: 1.0.0.Beta4
>
>
> By default, httpd.conf contains no configuration directives for the advertise module, yet advertise is enabled by default (i.e. ServerAdvertise default is On).  With no other configuration, JBoss's advertisement listener receives multicast messages with the header:
> X-Manager-Address: (null):0
> This is not very clean.
> If the advertise module cannot determine an advertisement address/port, then no multicast message should be sent at all (i.e. as if ServerAdvertise was Off), rather than sending a message with an invalid address.
> Since some kind of advertise directive is needed to indicate which address/port to use, why not default ServerAdvertise to Off?



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)