[jboss-jira] [JBoss JIRA] Closed: (JBAS-5698) Add RmiBindAddress to HANamingServiceMBean documentation
Samson Kittoli (JIRA)
jira-events at lists.jboss.org
Wed Dec 3 20:57:36 EST 2008
[ https://jira.jboss.org/jira/browse/JBAS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samson Kittoli closed JBAS-5698.
--------------------------------
Resolution: Done
fixed
> Add RmiBindAddress to HANamingServiceMBean documentation
> --------------------------------------------------------
>
> Key: JBAS-5698
> URL: https://jira.jboss.org/jira/browse/JBAS-5698
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Docs/Administration and Configuration Guide
> Affects Versions: JBossAS-5.0.0.CR2
> Reporter: Paul Ferraro
> Assignee: Samson Kittoli
>
> Previously, HANamingServiceMBean.bindAddress served two functions:
> From trunk/cluster/src/etc/hajndi-service.xml:
> <!-- Bind address of bootstrap and HA-JNDI RMI endpoints -->
> <attribute name="BindAddress">${jboss.bind.address}</attribute>
> The bootstrap and HA-JNDI RMI endpoints are now defined separately:
> <!-- Bind address of bootstrap endpoint -->
> <attribute name="BindAddress">${jboss.bind.address}</attribute>
> <!-- Bind address of the HA-JNDI RMI endpoint -->
> <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
> They each default to the same value.
> Users may want to override the RMI bind address if deployed on a multi-homed machine, and want to use an specific network interface for HA-JNDI RMI calls.
> This ability already exists in the standard NamingService.
--
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
More information about the jboss-jira
mailing list