tracker issue : CF-4201413

Problem Description:
 Suppose that Server Monitoring is disabled for your instance. For example, in the ColdFusion Administrator or, alternatively, in the file /lib/neo-monitoring.xml by means of the settings

<var name="monitoringenabled">
 <boolean value="false"/>
 </var>
 <var name="ismonitoringserverenabled">
 <boolean value="false"/>
 </var>

However, when you start up the instance, Server Monitoring ALWAYS starts, too, wiithin seconds. Irrespective of whether or not you had disabled Monitoring.

You can see this in /logs/monitor.log. During startup, a line similar to the following is written to that log file:

"Information","localhost-startStop-1","05/28/15","03:40:49",,"Starting Monitoring Server on port 55475."

It appears that ColdFusion looks up the available port at random. Occassionally, the result is an error, similar to the following (in /logs/monitor.log):

"Information","localhost-startStop-1","02/22/18","03:34:09",,"Starting Monitoring Server on port 63651."
 "Error","localhost-startStop-1","02/22/18","03:34:30",,"Unable to establish loopback connection"

This error always initiates a chain reaction of errors and exceptions, such as:

"Unable to establish loopback connection" >> "Could not initialize class coldfusion.runtime.SessionTracker" >> "The Monitoring service is not available."

See attached excerpts from monitor.log, coldfusion-out.log and coldfusion-error.log

Invariably, the instance's CPU usage increases steadily towards 100% of total CPU. This forces us to restart the instance.

Steps to Reproduce:

1. Create a cluster of several ColdFusion instances. Disable Server Monitoring in the ColdFusion Administrator or, alternatively, in the file /lib/neo-monitoring.xml

2. Start them up or program them to start up as Windows services at the same time every day.

3. Inspect monitor.log daily.

Actual Result:
 You will see that the monitoring service starts whenever an instance starts up. Occasionally, this results in the error "Unable to establish loopback connection". This error kicks off a chain of further errors and exceptions. Within hours, it leads to 100% CPU usage, bringing the entire server to a standstill.

Expected Result:
 If Server Monitoring is disabled for a ColdFusion instance, then the Monitoring service SHOULD NOT start during the instance's startup.

Any Workarounds:
 Restart the affected instance.

See also:
 [https://forums.adobe.com/thread/2428175]
 [https://tracker.adobe.com/#/view/CF-3837342]

Attachments:

1. March 05, 2018 00:00:00: Excerpt from coldfusion-error-log.txt
2. March 05, 2018 00:00:00: Excerpt from coldfusion-out-log.txt
3. March 05, 2018 00:00:00: Excerpt from monitor-log.txt
4. March 05, 2018 00:00:00: neo-monitoring-xml.docx

Comments: