[
http://jira.jboss.com/jira/browse/JBAS-4732?page=comments#action_12377154 ]
Brian Stansberry commented on JBAS-4732:
----------------------------------------
HANamingService exposes attributes "BindAddress" and
"AutoDiscoveryBindAddress", both of which are by default set to whatever you set
the -b startup switch to. Same as Naming and everything else.
Please open a forum thread to discuss if you are having issues with this.
Multihome support: HAJNDI`s HANamingServiceMBean needs a configurable
RmiBindAddress (like Naming`s MainMBean)
--------------------------------------------------------------------------------------------------------------
Key: JBAS-4732
URL:
http://jira.jboss.com/jira/browse/JBAS-4732
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.0.3 SP1
Reporter: Thomas Wenckebach
Assigned To: Brian Stansberry
Original Estimate: 1 day
Remaining Estimate: 1 day
For multihomed servers, it is essential to be able to bind JBoss services to dedicated
interfaces (bind address). This requirement is fulfilled by jboss service Naming, and all
other services known to the author, but not HAJNDI. Since this is an inconsistency in
implementing the design, I classify this to be a bug.
Affected source files:
$JBOSS_SRC/cluster/src/main/org/jboss/ha/jndi/HANamingServiceMBean.java
$JBOSS_SRC/cluster/src/main/org/jboss/ha/jndi/HANamingService.java
--
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