This can be partially fixed with setting this in jboss's run.conf as per
http://www.jboss.org/community/wiki/UsingJBossBehindAFirewall:
JAVA_OPTS="$JAVA_OPTS -Djava.rmi.server.hostname=<ExternalIP>
-Djava.rmi.server.useLocalHostname=false"
However, this breaks some MDB's (won't deploy, I suspect they try to get to
ExternalIP and that's not resolvable from behind the firewall).
Also, the client (Tomcat) still gets stuck while trying to bind to LocalIP:3873
which is the ejb3.deployer port -- from
server/all/deploy/ejb3.deployer/META-INF/jboss-service.xml:
<attribute
name="InvokerLocator">socket://${jboss.bind.address}:3873</attribute>
|
[/url]
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244637#4244637
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244637
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
