On Wed, Aug 24, 2011 at 7:57 PM, Jörn Kottmann <[email protected]> wrote:
> On 8/24/11 8:38 PM, Richard Eckart de Castilho wrote: > >> I recently had trouble connecting to a JMX server running on Linux (not >> EC2 though). It worked after I specified a "java.rmi.server.hostname" >> >> The parameters I used on the server side in the end were: >> >> -Djava.rmi.server.hostname=**192.168.0.25 >> -Dcom.sun.management.**jmxremote=true >> -Dcom.sun.management.**jmxremote.port=22222 >> -Dcom.sun.management.**jmxremote.ssl=false >> -Dcom.sun.management.**jmxremote.authenticate=false >> >> Maybe that'll fix it for you too. >> > > We once had a server which was moved from our local office network > to a data center, during the move the network interface was re-configured > and that caused later issues with JMX. > > Because somehow the following item was added to its hosts file: > 127.0.0.2 SERVERX.xxx.net SERVERX > > JMX tried to look up the ip address for its host name, and that was > then resolved to 127.0.0.2. > After removing the line it worked. > > Setting java.rmi.server.hostname property can help to identify such > problems, or just get it working. > > Jörn > Thank you Jörn and Richard. I will try your suggestions and come back with the results.
