I found out the issue.

In the file deploy/jms/uil2-service.xml, the parameter ${jboss.bind.address} 
resolves to the loopback address; by setting this to the actual IP address of 
the server the problem disappears (meaning I can now access the 
Queue/TopicConnection remotely so the message producer can send messages to the 
destination).

I tried adding this line to run.conf:
JAVA_OPTS="$JAVA_OPTS -Djboss.bind.address=`hostname`"

Also, tried using the actual ip address instead of 'hostname'; neither of these 
worked.

Question: Where the property ${jboss.bind.address} defined if not as a 
SystemProperty?  I grep'd the source but found no where that it is set.  I do 
not want to hardcode my IP address the file deploy/jms/uil2-service.xml.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944791#3944791

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944791


-------------------------------------------------------
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

Reply via email to