Title:
Error: Monitoring service is not available when multiple EAR files deployed at same time
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/Fixed
Reporter/Name(from Bugbase): Paul Cassar / Paul Cassar ()
Created: 01/23/2017
Components: Application Deployment
Versions: 2016,11.0
Failure Type: Non Functioning
Found In Build/Fixed In Build: CF11 / 2016.0.08.313320
Priority/Frequency: Normal / Some users will encounter
Locale/System: ALL / Linux RH Enterprise 6
Vote Count: 0
Problem Description:
When deploying multiple Coldfusion deployments as a J2EE Ear file on the same server, some of them may not start due to a conflict with the port for the Monitoring service. It seems that at first it tries with Port 5500, but if found to be occupied it will try another one. However, when the deployments are done at the same time (e.g. a reboot) it sometimes fails to assign a new port to a subsequent deployment. This forces the deployment to display an error "The Monitoring service failed to start".
Steps to Reproduce:
Install multiple deployments of Coldfusion as an EAR file on a single Jboss instance and restart them all at once.
Actual Result:
Some deployments intermittently fail because the port 5500 is taken by another deployment beforehand
Expected Result:
Deployments should all work as expected, with the monitoring port being locked as soon as an instance requests it. This would force other deployments to take a new port, hence solving the problem. Alternatively, the monitoring port should make use of the host container's (in our case Jboss 6.4) port offset to prevent any conflicts.
Any Workarounds:
If a server fails, manually restart it.Attachments:
Comments: