Comment 8 for bug 1774703

So, after getting reports of other issues today, bug 1773249 among them, and still seeing stuck apache2 websockets processes, we reverted both changes on our production system tonight. We are back to disconnect's old apache-websocket module and straight up OpenSRF 3.0.1. I suspect some of the issues we encountered will need to be addressed in the websocket module itself and some possibly in OpenSRF or Evergreen.