I need more info "Setting up Confluence" step "4. Enable JMX monitoring for your Confluence instance." That section of the documentation looks incomplete on
https://bitbucket.org/atlassian/elastic-experiment-executor/overview
However, I was able to start Confluence with jmxremote and connect to Confluence remotely with jconsole by using my own settings like this in setenv.sh
CATALINA_OPTS="-Dcom.sun.management.jmxremote.port=3333 ${CATALINA_OPTS}"
CATALINA_OPTS="-Dcom.sun.management.jmxremote.rmi.port=3333 ${CATALINA_OPTS}"
CATALINA_OPTS="-Dcom.sun.management.jmxremote.ssl=false ${CATALINA_OPTS}"
CATALINA_OPTS="-Dcom.sun.management.jmxremote.authenticate=false ${CATALINA_OPTS}"
CATALINA_OPTS="-Dcom.sun.management.jmxremote ${CATALINA_OPTS}"
I also connected jconsole using com.sun.management.jmxremote.authenticate=true
and supplied a username and password manually when connecting from jconsole.
1. But how does the test Framework use JMX monitoring for Confluence tests? Is it collecting data, changing attributes, running methods...etc?
2. what ports are used by the Test Framework to connect to JMX on my Confluence nodes, what type of authentication is used, and where in the Test Framework config files are the ports and login info entered for jmxremote connections to Confluence?