After trying several more permutations I finally got it to work with the ejbs
by changing the line
socket://${jboss.bind.address}:3873
to
socket://my_ip:3873
in ejb3.deployer/META-INF/jboss-service.xml.
Then similary for jms, I had to update it in the file:
jms/uil2-service.xml
I noticed that the jboss.bind.address was always 0.0.0.0
I then looked in the jboss invoker code and noticed that in the case that the
address passed into the invoker is 0.0.0.0 then it uses:
InetAddress.getLocalHost.getHostAddress()
to get the address to pass back to the session stub as the address to connect
to. On many linux distributions, the above code gives the result 127.0.0.1
while on windows it will give you the actual ip address of the machine. I
think that may have been why remote clients were attempting to connect to the
loopback address.
Rather than setting the ip of the machine in each of the files, is there a way
to just set jboss.bind.address??
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944794#3944794
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944794
-------------------------------------------------------
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
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
