For security reasons, Alfresco Content Services disables the remote JMX RMI connector by default. To connect remotely using a tool like JConsole, an administrator must explicitly enable this functionality. This is achieved by setting the alfresco.jmx.connector.enabled property to true in the alfresco-global.properties file and ensuring the related host and port properties are correctly configured. The problem described, where a connection attempt fails, directly points to this default disabled state.

A. The property alfresco.jmx.connector.enabled being set to true would enable the JMX connector, which is the opposite of the problem described.

C. JConsole is the standard Java monitoring tool included with the JDK and fully supports JMX Remoting (JSR-160) for connecting to remote MBean servers.

D. JConsole is a standard and officially documented tool for managing and monitoring Alfresco via JMX.

1. Alfresco Content Services 7.4 Documentation, Administering > Monitoring Alfresco > JMX settings. The documentation explicitly states: "The JMX RMI connector is disabled by default. To enable the JMX RMI connector, you must override the default settings..." It then lists the property alfresco.jmx.connector.enabled=false as the default.

2. Alfresco Content Services 6.2 Documentation, Administering > Monitoring Alfresco > Using the JMX command-line client. This section provides instructions for connecting with JConsole, confirming it is a supported tool. It also notes the requirement to enable the JMX connector first.

3. Oracle Java SE Documentation, Monitoring and Management Using JMX Technology > JConsole. This official source details the capabilities of JConsole, including its ability to connect to remote JMX agents, which is based on JSR-160.