tracker issue : CF-4141276

Duplicate ID:	CF-4141711

Problem Description:

Port ‘5500’ is available even though the Server Monitoring > Monitoring Settings > ‘Enable Monitoring Server’ from the administrator console is switched off. This feature works correctly on ColdFusion 9 and ColdFusion 10, the issue seems to be on ColdFusion 11 only. Issue has been tested on a fresh instance of ColdFusion 11 as well as with ColdFusion 11 containing update 7. 
As soon as the .ear file is undeployed the port is no longer available. 

When changing the IP address or port from the jetty.xml, the respective port is updated for the Monitoring Server Port, and thus it is being used by the Jetty service. An additional test was to listen to port ‘5500’ and the Monitoring Server Port is dynamically assigned to a new port. In ColdFusion 10 it used to give the error message that Port is already in use. As can be seen in the screenshots below the port is available even though the Enable Monitoring Server checkbox is unticked.


Steps to Reproduce:
1)  Disable Coldfusion Server Monitoring from Coldfusion Administrator
2)  Re-deploy Coldfusion EAR file
3)  Perform Port Scan 
4)  port 5500 will remain listening


Actual Result:

After disabling Coldfusion 11 Server Monitoring from the Coldfusion Administrator, the port 5500 remains open.


Expected Result:

The Jetty port 5500 should be disabled when Coldfusion Server Monitoring is off.  This is what currently happens on older various of Coldfusion.

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

Watson Bug ID:	4141276

External Customer Info:
External Company:  
External Customer Name: Godwin Schembri
External Customer Email:  
External Test Config: My Hardware and Environment details:



RHEL 6.5

Coldfusion 11 Update 7

JBoss 6.3 Enterprise Edition

Attachments:

1. April 18, 2016 00:00:00: 1_coldfusion_admin_settings.png

Comments: