How HQ Agent reads rmi server host ip - Help needed

[yadepu]

I am trying to understand how HQ Agent reads the RMI Server IP address. I tried to change in multiple places (conf/wrapper.conf) using -Djava.rmi.server.hostname, still It is trying to connect to jmx.url=service:jmx:rmi:///jndi/rmi://127.0.0.1:6969/jmxrmi}]:

I am getting following exception as a result.
org.hyperic.hq.product.MetricUnreachableException: Can't connect to MBeanServer [{jmx.password=springsource, jmx.username=admin, jmx.url=service:jmx:rmi:///jndi/rmi://127.0.0.1:6969/jmxrmi}]: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused: connect]

But I am running the tc server instance on VMware VM (virtual machine), how to overwrite the rmi server ip to reflect the virtual machine (but not the host machine).

Please help me in understanding how it works..
Thanks,
YA

Message was edited by: yadepu

[absorba]

You should be able to take the jmx.url, in your case - service:jmx:rmi:///jndi/rmi://127.0.0.1:6969/jmxrmi - and pass it in to jconsole. If it does not connect then something is wrong with your jmx url or your mbeans server.

In my experience, once I got the jmx url to work in jconsole it works in hyperic.