Just tried this setup on 9.0.6, and it worked.
OPTIONS=jmx
jetty.jmxrmihost=localhost
jetty.jmxrmiport=1099
-Dcom.sun.management.jmxremote
etc/jetty-jmx.xml
-Dorg.eclipse.jetty.jmx.MBeanContainer.LEVEL=DEBUG
Heck, I didn't even use --exec
The extra DEBUG entry enables debug logging for that class, so that I can see that the MBeanContainer is started.
$ java -jar start.jar
WARNING: System properties and/or JVM args set. Consider using --dry-run or --exec
2013-10-21 17:05:32.225:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.server.Server@31873729->qtp57003552{STOPPED,10<=0<=200,i=0,q=0}
...(snip)...
2013-10-21 17:05:34.399:DBUG:oejj.MBeanContainer:main: Registered org.eclipse.jetty.server:context=SSL-http/1.1@17ccbdbe,type=httpconfiguration,id=0
2013-10-21 17:05:34.400:DBUG:oejj.MBeanContainer:main: beanAdded HttpConnectionFactory@1f719a8d{HTTP/1.1}->org.eclipse.jetty.jmx.MBeanContainer@566749c5
2013-10-21 17:05:34.401:INFO:oejs.ServerConnector:main: Started ServerConnector@17ccbdbe{SSL-http/1.1}{
0.0.0.0:8443}
I can connect to it via jconsole, on the same machine that started the server, but oddly, port 1099 does not show up in netstat.