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

[Galder Zamarreno (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4604?page=all ]

Galder Zamarreno updated JBAS-4604:
-----------------------------------

    Workaround Description: 
There're 3 possible workarounds:

1.- remove XML override from AutoDiscoveryAddress, i.e:
<attribute name="AutoDiscoveryAddress">230.0.0.4</attribute>

2.- use a different XML override name so that jboss.partition.udpGroup confusion is avoided, but 
without setting this property on startup! :
<attribute name="AutoDiscoveryAddress">${jboss.partition.autoDiscoveryGroup:230.0.0.4}</attribute>

3.- set AutoDiscoveryGroup via jnp.discoveryGroup system property, see:
http://wiki.jboss.org/wiki/Wiki.jsp?page=NamingContextFactory

  was:
There's 3 possible workarounds:

- remove XML override from AutoDiscoveryAddress, i.e:

<attribute name="AutoDiscoveryAddress">230.0.0.4</attribute>

- use a different XML override name so that jboss.partition.udpGroup use is liberated:

<attribute name="AutoDiscoveryAddress">${jboss.partition.autoDiscoveryGroup:230.0.0.4}</attribute>

- set AutoDiscoveryGroup via jnp.discoveryGroup system property, see:

http://wiki.jboss.org/wiki/Wiki.jsp?page=NamingContextFactory


> NamingContext does not take potential AutoDiscoveryAddress XML property overrides when sending discovery requests
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4604
>                 URL: http://jira.jboss.com/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-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: Brian Stansberry
>            Priority: Minor
>
> 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

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira