Overview

Java Management Extensions (JMX) is a Java technology that supplies tools for managing and monitoring applications, system objects, devices (such as printers), and service-oriented networks.

You may have a requirement to turn off JMX on your Jive instance if it has been enabled. This article provides step-by-step instructions on how to disable JMX on Jive on-premise instances.

Information

1. Please plan for a downtime window for this change as it would require restarting all webapp nodes.
2. Log in to each webapp node switch to the jive user:
   

   $ sudo su - jive

3. Then execute the following command and make a note of the current setting (to revert back in case of a failure):
   

   $ jive list | grep jmx

4. Execute the following commands to set the properties to disable JMX:
   

   $ jive set docconverter.jmx_enabled False
   $ jive set ingress-replicator.jmx_enabled False
   $ jive set search.jmx_enabled False
   $ jive set eae.jmx_enabled False
   $ jive set webapp.jmx_enabled False

5. Run the following command again and verify that the changes are applied.
   

   $ jive list | grep jmx

6. After you have applied all the settings, proceed to restart the webapp node with:
   

   $ jive restart

   JMX is used for diagnostic purposes and can be used to connect via VisualVM console to grab heapdumps or threaddumps. If you need to use these tools in the future again, you can enable JMX by setting the properties in step 4 to True and subsequently restarting the webapp nodes.