tracker issue : CF-4130808

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

Monitoring Server Listens to Port 5500 even when disabled from Admin

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Andreas Säckl / Andreas Säckl (Andreas Säckl)

Created: 03/21/2016

Components: Server Monitoring

Versions: 2016

Failure Type:

Found In Build/Fixed In Build: CF2016_Final /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Windows 10 64 bit

Vote Count: 0

Duplicate ID:	CF-3837342

Problem Description: Monitoring Server Listens to Port 5500 even when disabled from Admin neo-monitoring.xml also has value of <var name='ismonitoringserverenabled'><boolean value='false'/>

Steps to Reproduce: WAR deployment under stock wildfly-9.0.2.Final

Actual Result: Server Monitoring is started no matter how you set/unset the Enable Monotorisn Server flag.

Expected Result: Monitoring server not to start when disabled flag is set.

Any Workarounds: Need Monitoring server not to run as it forces Wildfly not to shutdown properly.

Same bug as bug #3837342.

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

Watson Bug ID:	4130808

External Customer Info:
External Company:  
External Customer Name: Andreas Säckl
External Customer Email:  
External Test Config: My Hardware and Environment details:

Windows 10 1511 64bit

Stock wildfly-9.0.2.Final

Java 1.8.0_73

Attachments:

Comments:

Closing this bug marking duplicate of bug# CF-3837342. As stated in bug# CF-3837342 Port number 5500 is used internally for some other services. Even if the monitoring module is disabled the port would be used for other services. Hence, in order to avoid confusion this port number information is removed from the Monitoring Settings Admin page.
Comment by Dattanand M.
3259 | April 01, 2016 07:01:26 AM GMT