Hi Tom, I did some further testing, when I set up a cluster on a single machine, the Bindingmanager assigns port 3873 and 4073 for the Connector defined in "/EJB3Deployer/META-INF/jboss-service.xml". When I kill the first node, 3873 is of course gone and the app fails. Just running node 2 shows, the Interfaces InvokerLocator property still trys the 3873 port , even though it has never been set for that node. This also shows up when both servers are running, then the 2 InvokerLocator elements in the interfaces array are both the same (and not 3873 and 4073).
I also have another question: after looking at the InvokerLocator's method "private static final String resolveHost(String host)", I think that the host name will always be looked up to the IP address of the current machine (I guess do too performance reasons) (or did I miss something?). Is it possible to avoid this? I thing in a scenario were each IP Addresses of the JBoss servers should or is not visible to the outside, is imaginable (e.g. Client goes over the I-Net to the Servers). Then this would lead to an invocation failure since the ip is not resolvable to the client. Please correct me if I am wrong, I am still missing quite a bit of over view over all this. Sincerely Marc View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942807#3942807 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942807 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
