JBoss usually binds its services to only one network interface. You can check on which interface JBoss listens with:
(Linux) netstat -ant
(Win32) netstat -an -p tcp
You should get something like:
TCP 127.0.0.1:1098 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1099 0.0.0.0:0 LISTENING
which in this case means JBoss only listens on the local loopback interface but not on the public IP address of that machine.
The ports are definately open and I can tell from Ethereal that it is connecting and getting an RMI reply from JBoss.
1099 is our naming service port. We don't run an rmi registry, so you need to see what instructions visualgc (which I have not used) has for configurating its use.
Thanks for that Scott. I'll see what I can do with a seperate RMI Registry.
I'll be sure to post back info here if/when I work it out because the visualgc tool is very handy.