anchor.diff:  [source]
   ----
   SUNJMX=-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1616 \
  --Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
  +-Dcom.sun.management.jmxremote.access.file=<path.to.jmx.access> \
  +-Dcom.sun.management.jmxremote.password.file=<path.to.jmx.password> \
  +-Dcom.sun.management.jmxremote.ssl=false
   ----
   
   (The SUNJMX environment variable is simple used by the startup script
  
positive.code:  set CATALINA_OPTS=-Dcom.sun.management.jmxremote \
      -Dcom.sun.management.jmxremote.port=1099 \
      -Dcom.sun.management.jmxremote.ssl=false \
      -Dcom.sun.management.jmxremote.authenticate=false
  ----
  
  === JBoss AS 4
  
negative.code: 
  [CAUTION]
  Starting from Camel 3.2.0, the configuration in this section no longer applies. For older
  releases, it is strongly recommended not to use this functionality for security reasons. Instead,
  use the default JVM JMX remote capabilities if required.
  
  JMX connector server enables MBeans to be remotely managed by a JMX
  