Hi Tom, i created a new testcase to find out more about this issue. I've used 4.0.4GA from source and created an servlet-invoker.war from JBoss-Remoting 1.4.1. I've done several tests with socket and servlet (http) protocol and found the difference inside HttpClientInvoker and SocketClientInvoker. So in HttpClientInvoker the originalURL is used to connect from Client to Server (to call methods on an ejb3 bean clientBindUrl is used), as in SocketClientInvoker the host is used, which will always be resolved to ip-adress inside the InvokerLocator. So i think that in an Client=>Firewall=>JBoss environment this behaviour is ok as far as you were using the http protocol which should be the favourite. So in my opinion the problem could only occure if someone is using socket - transport instead of http. To quickly get an workaround about the @RemoteBinding clientBindUrl issue (EJB3-RC8 is not released yet), i defined an property named clientBindUrl.default where i can define an default URL for all EJB3-Bindings. This property is set at server-startup and is independent from InvokerLocator-URL (jboss-service.xml) as i thought about to use as default before. This because we use an Apache-Server for http and the ejb3.deployer is bound on port 8080, but clients must call ejb3's over port 80.
Kind regards, Heiko View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947333#3947333 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947333 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
