Problem Definition

The Engine name on Tomcat's server.xml is set to Standalone by default in Confluence:

<Engine name="Standalone" defaultHost="localhost" debug="0">

This configuration does not allow for exposing MBeans for remote Jconsole JMX monitoring.

Suggested Solution

Using the Engine name as Catalina (as Jira currently does) allows for out-of-the-box remote Jconsole JMX monitoring.

There are no known downsides to switching the Engine name.

Workaround

Manually edit Tomcat's server.xml to switch the Engine name from Standalone to Catalina:

<Engine name="Catalina" defaultHost="localhost" debug="0">

After the changes are done, restart Confluence.

If running Confluence DC, repeat the same procedure for each node in the cluster.

PS: The same steps need to be taken after a Confluence upgrade for JMX monitoring to keep working.