[jboss-jira] [JBoss JIRA] Closed: (JBAS-3257) HANamingService: Enable definition of RmiBindAddress analogous to RmiBindPort

[Brian Stansberry (JIRA)]

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

Brian Stansberry closed JBAS-3257.
----------------------------------

    Resolution: Duplicate Issue
      Assignee:     (was: Jerry Gauthier)


Duplicates JBAS-4732

> HANamingService: Enable definition of RmiBindAddress analogous to RmiBindPort
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-3257
>                 URL: https://jira.jboss.org/jira/browse/JBAS-3257
>             Project: JBoss Application Server
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>         Environment: Solaris, use gnu patch to apply patchfile:
> /opt/gnu/bin/patch < patch.txt
>            Reporter: Jerry Gauthier
>         Attachments: patch.txt
>
>
> Reported by Thomas Wenckebach - see JBCLUSTER-94
> Consider the following setting:
> In multi home cluster environments you might want to bind the HANamingService Port to a High Available (virtual) IP address, whereas the NamingService Port would be a local ("real") IP address in this case (different LANs). Note that it is strictly mandatory in this setting to also bind the RmiPort of HANamingService to a local IP address, since it is referenced internally via the system property java.rmi.server.hostname - a conceptual flaw, since it is also used for referencing the NamingService. Consequently, it is a must to bind both NamingService and HANamingService RmiPorts to the same interface. From this fact follows the necessity to bind HANamingService RmiPort to an interface different from the one used by HANamingService Port!
> Simply do the following:
> $> cd jboss-4.0.3SP1-src/cluster/src/main/org/jboss/ha/jndi
> $> /opt/gnu/bin/patch < patch.txt
> ( please find patch.txt attached! )

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