[jboss-jira] [JBoss JIRA] Updated: (JBAS-4604) NamingContext does not take potential AutoDiscoveryAddress XML property overrides when sending discovery requests

NamingContext does not take potential AutoDiscoveryAddress XML property overrides when sending discovery requests ----------------------------------------------------------------------------------------------------------------- Key: JBAS-4604 URL: https://jira.jboss.org/jira/browse/JBAS-4604 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Components: Clustering, Naming Affects Versions: JBossAS-4.0.5.GA, JBossAS-5.0.0.Beta2, JBossAS-4.2.1.GA Reporter: Galder Zamarreno Assignee: Brian Stansberry Priority: Minor Fix For: Backlog Bug in org.jnp.interfaces.NamingContext: discoverServer(Hashtable) method String group = DEFAULT_DISCOVERY_GROUP_ADDRESS; ... String discoveryGroup = (String) serverEnv.get(JNP_DISCOVERY_GROUP); if (discoveryGroup != null) group = discoveryGroup; ... iaGroup = InetAddress.getByName(group); .... if (trace) log.trace("Sending discovery packet(" + data + ") to: " + iaGroup + ":" + port); NamingContext code does not take in account possible system property overrides coming from: <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute> AutoDiscoveryAddress used to send discovery messages is controlled via the the default value, 230.0.0.4 or jnp.discoveryGroup property. So, if user sets jboss.partition.udpGroup=224.0.0.1 on startup, DetachedHANamingService$AutomaticDiscovery will listen on 224.0.0.1 while NamingContext sends discovery requests to 230.0.0.4