I'm starting jmx with the following jmx options:
JAVA_OPTS="-Djavax.management.builder.initial=org.jboss.mx.server.MBeanServerBuilderImpl" JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver" JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=12345" JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=true" JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.password.file=/path/to/jmxusers.properties" JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.access.file=/path/to/jmxusers.properties" JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false" JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver" export JAVA_OPTS $JBOSS_HOME/bin/run.sh -b myhostname -c myservername
If you really want this workaround implemented, why not submiting a patch? :)