Coldfusion version required for cfwebsocket

[ChrisGaelic]

I'm using CF11 Standard and need to use websockets. Do i need to upgrade to the Enterprise version to do this?

[WolfShade]

According to this support page, there is nothing mentioned about it only working in Enterprise CF.  I would suspect the standard CF deployment supports it.

HTH,

^ _ ^

[WolfShade]

I'm using the Developer Edition, and can confirm that the Websockets is available in DE.

V/r,

^ _ ^

[Dave Watts]

Developer Edition basically has all the features of Enterprise, so I'm not sure that means a lot.

Dave Watts, Fig Leaf Software

[nic_tunney]

Searching online I also see no restriction by Standard vs Enterprise, although I thought there was.  I believe back in CF 10 when the feature was introduced, there was a 100 connection limit for Standard edition.  For CF 2016 the buying guide only seems to represent cluster support for web sockets as an Enterprise-only feature.  Not sure where this leave CF11.  The buying guide for CF 11 standard listed websocket support for standard, but it was not quite as clear: https://www.adobe.com/products/coldfusion-standard/buying-guide.html

-Nic

[ChrisGaelic]

Thanks guys. I've been unable to get cfwebsocket to work. It doesn't generate an error, but processing stops after that tag. I was just attempting to run Awdhesh Kumar's example code. But then I noticed that he said that CF 2016 Enterprise edition was required. Hence my question. CF Admin included all the setup items for websocket setup, and I couldn't find anywhere else that suggested that it was restricted to the Enterprise version. Hence my question.

[Charlie Arehart · Accepted solution]

First to clarify, Nick is right. WebSockets are absolutely supported in Std or Ent, and yes, with the original release of the support with CF10 the Std edition had a throttle of 100 simult requests. That was lifted in 11 (and of course remains “lifted” in 2016), but yes the clustered support feature remains Ent-only.

As for your challenge and your last note, are you accessing it via your external web server (IIS or Apache), or the internal CF web server (port 8500, by default)? If the former, there is additional work to be done in both the Admin and in setting up a connector for websockets. Have you attended to those?

Also, since you say processing “stops after the tag”, are you saying that you put some other processing after that (like a cfdump or cflog) and you can confirm that does NOT run? And in that you say that it “doesn’t generate an error”, do you mean on screen? Or do you mean you have checked all the CF logs when this happens? (BTW, don’t trust the date/time modified on the logs. Open the top 5-10 of them and go to the bottom to make sure there’s no error info about the problem.)

/charlie

[ChrisGaelic]

Hi Charlie,

Thanks for confirming that it should run. No, I haven't done any additional setup, having only looked in CF Admin, which appeared that everything was set up ready to go. It is on my external webserver, Also, I placed a cfdump before the cfwebsocket tag, and then after it. The first one displayed a result, but the second one didn't. And I did check the error logs and didn't see anything relevant.

[Charlie Arehart]

I replied to Chris separately (he had emailed me directly, as we have traded emails before). Since he is wanting to have CF websocket processing happen by way of his external web server (IIS or Apache), he needs to enable that in both the CF Admin and the CF web server connector. I pointed out to him that if he just googles:

coldfusion websockets IIS

The first several results show what needs to be done.

/charlie

[ChrisGaelic]

Just a follow-up to complete this, I'm currently running IIS 7.5, which doesn't support websockets. So, I need to upgrade my webserver to at least windows server 2012 and IIS 8.

Chris