FIXED! The solution is to use the following annotation in your bean: @RemoteBinding(clientBindUrl="socket://public.host.address:3873")
The port 3873 is defined in the file server/all/deploy/ejb3.deployer/META-INF/jboss-service.xml: <server> | | <mbean code="org.jboss.remoting.transport.Connector" | xmbean-dd="org/jboss/remoting/transport/Connector.xml" | name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler= | ejb3"> | <depends>jboss.aop:service=AspectDeployer</depends> | <!-- attribute name="InvokerLocator">socket://0.0.0.0:3873</attribute --> | <attribute name="InvokerLocator">socket://0.0.0.0:3873</attribute> | <attribute name="Configuration"> | <handlers> | <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvoc | ationHandler</handler> | </handlers> | </attribute> | </mbean> | ... | The following is the best thread I found on this topic is here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3877360. However, in contrast to that thread, I found that I did not need to explicitly state the external ip address in the above file. The default setting of 0.0.0.0:3873 works, which is good. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930837#3930837 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930837 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
