We have a JBOSS 5.1 EAP implementation with multiple queues . Currently all clients are internal clients and access the queues by performing local network lookups.
New requirement to provide access to External remote client on a different network .
JBoss server 5.1 / local IP :10.x.x.x / hostname : xyz.com
Local clients access by invoking jnp://10.x.x.x:1099 or jnp://xyz.com:1099 and are able to post/consume messages.
We have an external client for which we have a VPN tunnel created a VPN tunnel and they have mapped our hostnames with their local IPs
i.e xyz.com 164.y.y.y ( 164.y.y.y is not accessible by the JBOSS server 5.1)
while accessing JMS : jnp://164.y.y.y:1099 or jnp://xyz.com:1099 we get an error
“Could not obtain connection to any of these urls: 164.y.y.y:1099 and discovery failed with error:
javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]”
From external client - telnet to all the ports work also a wget to http://xyz:8080 / returns a result.
Question :
- Any jboss settings to change
- Any other way for external remote clients to connect to JBOSS JMS ?
a)We have already tried clientConnectAddress", "clientConnectPort", in the remoting-bisocket-service.xml but since external 164.y.y.y.y is not accessible from internal network it breaks
b)Also tried -Djava.rmi.server.hostname=<external ip> -Dremoting.bind_by_host=false to the run script , same issue.
Above suggestions breaks access to local in-network clients
