tracker issue : CF-3998747

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

CF Express and port conflicts

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Raymond Camden / Raymond Camden (Raymond Camden)

Created: 06/01/2015

Components: Getting Started Server

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: CF11_Final / 296247

Priority/Frequency: Normal / Some users will encounter

Locale/System: English / Mac 10 All

Vote Count: 0

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on February 18, 2019 using build 2016.0.01.298513 
Start ColdFusion ENT/STD, or heck, anything that takes the same port as CF Express, and then start CF Express. It will report:

Starting ColdFusion 11 server ...
The ColdFusion 11 server is starting up and will be available shortly.
======================================================================
ColdFusion 11 server has been started.
ColdFusion 11 will write logs to /Users/raymondcamden/Downloads/ColdFusion/cfusion/bin/../logs/coldfusion-out.log
======================================================================

But while maybe the Java stuff started, you can't actually hit the site because of the port conflict. The startup script should be intelligent enough to recognize this error and throw a *useful* message to the user.

Let me be clear, the error should be *useful*, not a giant stack trace.

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

Watson Bug ID:	3998747

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

Attachments:

Comments:

It's not a bug. It's mentioned in the "Readme.txt" at \ColdFusion_exp_11_WWEJ_win64\ColdFusion\Readme\ for CF Express, that:- 2) The ColdFusion Administrator will be accessible on port 8500. In case the port needs to be changed, it can be done in the ColdFusion\cfusion\runtime\conf\server.xml file So, you need to change the port, if it is already being used by any other service, not necessarily ColdFusion only.
Comment by Anit K.
7282 | June 01, 2015 01:16:20 PM GMT
I didn't say it was a bug that it couldn't magically fix the port conflict, I get that the app can't kill the other app or fix it, but something in CF saw the conflict and it wasn't reported to the user. How would I know something went wrong? The command line told me it worked, right?
Comment by External U.
7283 | June 01, 2015 01:24:17 PM GMT
Also, did you tell the user what line to change in server.xml? I know it only exists once, but you should be explicit in the readme to make it obvious.
Comment by External U.
7284 | June 01, 2015 01:25:42 PM GMT
We will fix the readme.txt to be more explicit. Thanks Ray.
Comment by Vamseekrishna N.
7285 | June 04, 2015 08:09:00 AM GMT
Good to know, but what about the port conflict?
Comment by External U.
7286 | June 04, 2015 08:14:02 AM GMT
The fix will be available in the next Coldfusion release.
Comment by Mukesh K.
7287 | November 03, 2015 04:38:03 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). The Readme.txt is now more explicit. Unable to verify the described "ColdFusion 11 server has been started." message, when port 8500 was already being used by another service (i.e. another CF running), b/c Express Edition's cfstart.bat always failed to run in that scenario. Thanks!, -Aaron
Comment by Aaron N.
30303 | February 18, 2019 03:28:55 AM GMT