Documentation bug: Missing arguments for JMX Monitoring article for modifying setenv.sh/.bat

Issue Summary

This applies to the documentation at:
Live monitoring using the JMX interface

See the section Monitoring Jira remotely

For customers who use JAVA_OPTS (instead of CATALINA_OPTS) within setenv.sh/.bat, our documentation is not so helpful.

Expected Results

The syntax for JAVA_OPTS would be included in addition to CATALINA_OPTS

Actual Results

Only CATALINA_OPTS is mentioned in the article

Notes

For more context see serverfault article Tomcat : Where to configure jmx JAVA_OPTS or CATALINA_OPTS

Workaround

Add the following arguments to setenv.bat or setenv.sh:

For Windows, setenv.bat
JAVA_OPTS=-Dcom.sun.management.jmxremote %JAVA_OPTS%
JAVA_OPTS=-Dcom.sun.management.jmxremote.port=8099 %JAVA_OPTS%
JAVA_OPTS=-Dcom.sun.management.jmxremote.authenticate=false %JAVA_OPTS%

For Linux, setenv.sh
JAVA_OPTS="-Dcom.sun.management.jmxremote ${JAVA_OPTS}"
JAVA_OPTS="-Dcom.sun.management.jmxremote.port=8099 ${JAVA_OPTS}"
JAVA_OPTS="-Dcom.sun.management.jmxremote.authenticate=false ${JAVA_OPTS}"
export JAVA_OPTS