Following my question earlier about HTTP tunnelling, I can see why I got no response: JBossMQ is simply meant for peer processes on a single LAN subnet - and localhost is ideal!!

I hope I have this wrong, but I don't think so!

Three points:

+ java.naming.provider.url=remotehost:1099 needs to be set to get you going - fine.
+ java.rmi.server.hostname=remotehost to get the 1099 port to return a good IP if you have multiple net interfaces - fine. Can set rmiPort too, if you want.
+ In JMS: OIL has to have the bindAddress set before things get going: it doesn't seem to work setting it late in the port 8082 management pages - not fine (code change)! Again, only if you have multiple net interfaces and the first one looked-up is the wrong one.
+ The killer: ping-pong! JMS goes back from port 8090 to the arbitrary port on your machine when starting work (e.g., subscribe to Topic). Even without NAT port-mapping problems, not many firewalls will allow this.

OK - someone tell me I'm wrong and WAN JMS is actually a possibility. Then we can start talking about HTTP tunnelling!!!!!

Duncan Cragg