Java – Remote JMX connections are sent to localhost

I' m trying to set up remote JMX monitoring on a Java process. These are the options I'm giving the JVM to start it:

JAVA_OPTS="-server -Xms1G -Xmx1G -XX:MaxPermSize=512m "
JMX_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=57011 -Dcom.sun.management.jmxremote.authenticate=false"
JMX_OPTS="$JMX_OPTS -Dcom.sun.management.jmxremote.ssl=false -Dfoo.jmx=true -Dfoo.jmx.detailed=true"
JMX_OPTS="$JMX_OPTS -Djava.rmi.server.host=192.168.9.121"
LOG_OPTS="-Dfoo.logging.type=log4j -DLOGDIR=${SERVERDIR}/logs"
ASD_OPTS="-Dfoo.conf.file=file:${PROPFILE} -cp ${CLASSPATH} foo"
/usr/bin/nohup ${JAVA_EXE} $JAVA_OPTS $JMX_OPTS $LOG_OPTS $ASD_OPTS 1>${SERVERDIR}/service.log 2>&1 &

I'm able to connect using Jconsole locally, but when I connect from a remote host, I get following error (cut for brevity's sake)

Java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: 
java.net.ConnectException: Connection refused: <snip>

So despite the explicit declaration saying to bind to 192.168.9.121 (-Djava.rmi.server.host), JMX is still binding to the remote system's loopback interface.

The only workaround I've found is to modify my /etc/hosts to set the system's FQDN like so:

127.0.0.1       localhost localhost.localdomain
192.168.9.121   my.servers.fqdn.com

Based on the fact that every Linux system I've ever seen has "my.servers.fqdn.com" pointing at 127.0.0.1, I can only imagine weird problems with changing this.

How can I get remote JMX monitoring working without this hack?

The system is CentOS 6, Java 1.6.0_35, firewall disabled for testing.