I'm seeing a testsuite failure for the binding manager examples.

http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite/20050907123703/results/org/jboss/test/binding/BindingServiceUnitTestCase.html

junit.framework.AssertionFailedError: All services are started, errors=1
 at org.jboss.test.binding.BindingServiceUnitTestCase.testAvailableServices(BindingServiceUnitTestCase.java:116)
 at org.jboss.test.binding.BindingServiceUnitTestCase.testAvailableServicesServer1(BindingServiceUnitTestCase.java:65)

Looking at the logs for binding-manager2 (ports-02), it seems to be trying to bind HAJNDI to port 1101:

http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite/20050907123703/build/output/jboss-4.0.3RC2/server/binding-manager2/log/server.log

2005-09-07 13:56:53,440 DEBUG [org.jboss.ha.jndi.HANamingService] Starting failed jboss:service=HAJNDI
java.rmi.server.ExportException: Port already in use: 1101; nested exception is:
 java.net.BindException: Address already in use

But the logs for binding-manager1 (ports-01) show that port is already taken:

2005-09-07 13:56:22,157 DEBUG [org.jboss.system.ServiceConfigurator] RmiPort set to 1101 in jboss:service=HAJNDI

But in the sample-bindings.xml, the HAJNDI RmiPort was overriden to be ports 1198 and 1298 for ports-01 & ports-02 respectively?

 <service-config name="jboss:service=HAJNDI"
 delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
 >
 <delegate-config portName="RmiPort"/>
 <binding port="1298"/>
 </service-config>

Why isn't this being respected?