How to find Tomcat MBeans on Confluence JMX interface

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Tomcat MBeans are quite useful for monitoring. Normally, they are found under the Catalina sub-tree, but that is not true for Confluence.

This is related to the Engine name set by default on the server.xml file:

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

Solution

When looking for those MBeans in the Confluence JMX interface, just expand the Standalone subtree as shown below:

(Auto-migrated image: description temporarily unavailable)

While it should be possible to edit the server.xml file and set a different name, we would not recommend that. This is because other files might reference the engine name, and it also creates another customization to reapply after every upgrade.

Updated on February 19, 2025

Still need help?

The Atlassian Community is here for you.