We are back with a solution to another, perhaps not so widely known bug. This time it’s a ColdFusion native bug involving its own websocket and session variables. Frankly, it was bugging us (no pun intended)  for the past 2 years. Here’s the problem in detail:

We are running an application that utilises ColdFusion’s native websockets functionality. In a most basic scenario, we run a cfcomponent with several functions to create a notification record and insert it in the database. Then, as one would, push it via the webscoket so all the connected users with the relevant permissions receive it instantaneously. All is nice and well, right? NO.