[jula]

Let me rephrase:

If my JBoss 3.2.3 server is on a LAN where the Internal IP is not exposed to outside (using NAT) and my client is on another LAN (again using NAT): is it possible for my client to access JMS queues' the server using HTTP Tunneling?

If so, what are the changes that I have to do on configuration (XML) files on the server side?

TIA
/Jula

[ajordens]

I'm having similar problems with the HTTPConnectionFactory.

JBoss is running on an internal NAT'd machine. I need to be able to run JMS over 8080 to facilitate someone from outside the firewall to be able to receive messages.

I've made the following client side changes:

Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.HttpNamingContextFactory");

props.put(Context.PROVIDER_URL,
"http://10.1.15.5:8080/invoker/JNDIFactory");

props.put( "java.naming.rmi.security.manager", "no");
props.put( "jnp.disableDiscovery", "true");

Right now, I'm considering 10.1.15.5 to be the outside ip address.

On the server, I have made changes to the http-invoker.sar/META-INF/jboss-service.xml

and set the InvokerURL to be based on the machines local ip address. I have tried both local and remote ip addresses without much luck.


I'm wondering what settings are appropriate for the client side and server side in order to get JMS out through 8080 in a NAT'd environment.

Much appreciated,
Adam.

[jkerr]

I'm working with Adam on this problem and wanted to add a little clarification on all the pieces of this puzzle and what we're trying to accomplish.

Let's say that we're dealing with two groups of IP addresses:
Behind firewall: 192.x.x.x
and the client requests will originate from 137.x.x.x
and suppose the address of the JBoss server is 192.1.1.10

The way that the NAT is set up (which we have no control over) forwards requests originating from 137.x.x.x for ports 8080 and 4444 to 192.1.1.10 while any request originating from 192.x.x.x is routed somewhere else.

We can use force a particular address to be used via the file deploy/http-invoker.sar/META-INF/jboss-service.xml but will only work in the favor of either the client or the MDB (set it to 192.1.1.10 and the MDBs are happy but the client can't resolve the address. Use the external address and the client can connect but the MDB gets redirected into never never land)

Is there any way to specify one address for the client and another for the MDB?

Jon

[adrian.brock]

Which part of the following section from the "Read this first" topic did
you or Adam not understand?

Do not post ME TOO . If you have the same problem but nothing
to add to the problem, don't add noise to the thread!

Always start a new thread for a new problem. Do NOT hijack
somebody's problem. Try to keep to one question per thread,
it is easier for others to follow.

You are not helping Jula so why are you posting on his/her thread?

[marat]

There is a third party solution available that allows you to run most of J2EE APIs over HTTP(S).

Have a look at http://www.jproxy.com

Cheers,
Marat