tracker issue : CF-4176625

select a category, or use search below
(searches all categories and all time range)

Monitoring Service Error

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Ramesh Balajepalli / Ramesh Balajepalli (Ramesh Balajepalli)

Created: 07/28/2016

Components: ColdFusion Services

Versions: 2016

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF2016_Update2 /

Priority/Frequency: Normal / Some users will encounter

Locale/System: English / Windows 8.1/64bit

Vote Count: 0

Listed in the version 2016.0.03.300466 Issues Fixed doc
Problem Description:All webpages including admin screen throws monitoring service error

Steps to Reproduce:in a multi cluster environment, start all instances at same time and access either a webpage or CFADMIN screen.

Actual Result:Throws an 500-Internal server error ( The monitoring service is not available. )

Expected Result: Screen gets loaded with no errors.

Any Workarounds:Restart services one at a time.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4176625

External Customer Info:
External Company:  
External Customer Name: Ramesh Balajepalli
External Customer Email:  
External Test Config: My Hardware and Environment details:It seems monitoring service port on all CF instances were set to start on port 5501. If its in use, the instance gets a new port. This work fine when we start one instance at a time, but if all of them start at same time, there will be a port conflict and the instance starts throwing error message. The port is set in Jetty.xml file and every instance should have a new port assigned.


  1. March 05, 2018 00:00:00: 1.PNG


As per your comment: if all of them start at same time, there will be a port conflict and the instance starts throwing error message. What do you mean by starting all the instances at the same time. Can you give the steps of reproducing this bug.
Comment by HariKrishna K.
2089 | July 28, 2016 11:14:53 PM GMT
Can you please revert with the info?
Comment by HariKrishna K.
2090 | August 08, 2016 04:25:59 AM GMT
Hi Hari, Steps to reproduce. 1) Setup multi instance CF cluster on windows VM and have the services run as windows service. 2) Reboot the server. 3) Look at monitor.log under each instance and all of them tires to start on port 5501 and if its busy, it gets a random port. 4) In few scenario's, that throws an exception JVM_bind exception, port already in use.
Comment by External U.
2091 | August 08, 2016 09:18:30 AM GMT
This fix will be available in ColdFusion 2016 Update3. The fix would be, now whenever we create new instances, unique port would get assigned to jetty server and hence there would not be any problem in case of a restart. Note: This fix will not work with the existing instances.
Comment by HariKrishna K.
2092 | August 11, 2016 02:55:33 AM GMT
We have found this same issue. Manually changing the ports in jetty.xml to known unused ports has helped us alleviate the issue.
Comment by External U.
2093 | October 03, 2016 07:12:13 AM GMT
BTW, I appreciate this is being fixed, however this is an issue in other areas... Web Socket Ports - they increment on the 2nd instance 8579, 8580, 8580, 8580, etc Flash Fallback Port for Web Sockets - Same thing. 1243, 1244, 1244, 1244, etc
Comment by External U.
2094 | October 06, 2016 01:58:41 PM GMT