Problem Description :- There are users who would like to setup monitoring of the internal Java Virtual Machine (JVM) processes used in Adobe Connect. Typically the JVM which can be managed and monitored using Java Management Extensions (JMX) but requires configuration to enable a port, username and password to use JMX. Typically, this configuration is done as part of the Tomcat installation. Since Adobe Connect uses a customized deployment of Tomcat users need to know which files and configuration properties they need to modify to enable this feature in Adobe Connect.
Refer to following settings in <Connect_home>/appserv/conf/ConnectProSvc.conf file
Look for snippet :-
# Remote JMX connections (uncomment to enable remote JMX access; unauthenticated as-is)
After changes restart CPS Services.
The JVM wrapper config changes above will provide the ability for a JMX client to connect to the server, but the actual ability for management/monitoring will be generic and barebones. In order to ensure that Connect-specific mbeans are exposed/managed/monitored, you will also need to ensure that the following configuration exists in, e.g., your custom.ini:
Because If it doesn’t exist, it defaults to false.
To enable password protection of the remote JMX connections ( Hope this link below would help ) :- https://blogs.oracle.com/lmalventosa/entry/jmx_authentication_authorization
Here is a link which would help understand the entries such as shown below like in connectprosvc.conf file :-
# Log Level for sys/event log output. (See docs for log levels)