evostreamms does not utilize more than one process

Not sure if this could be related, but would it be possible that the EMS thinks there are no connections to it therefore doesn’t utilize the other spawned processes? There are over 1,000 clients connected to my EMS instance right now yet calling clientsConnected on the API returns the following:

{“data”:{“outboundCount”:0},”description”:”EMS outbound client connections count”,”status”:”SUCCESS”}

I have RTMP commented out in the config.lua, I configured this EMS instance to only allow WebSocket clients. So, I thought “okay, WebSockets are technically HTTP. Let’s try calling httpClientsConnected” Here is that result:

{“data”:null,”description”:”Unable to get count of all open HTTP streaming sessions”,”status”:”FAIL”}

Next up I tried getConnectionsCount. The result:

{“data”:{“count”:1266},”description”:”Active connections count”,”status”:”SUCCESS”}

I know for a fact those 1266 are not all inbound connections. Far from it. This issue is the only thing preventing me from purchasing more EMS licenses to roll out across all of my live streaming sites. Is there a way we can jump on a Slack channel for quicker communication regarding this issue?

Any update on this? 

The EMS does not currently “cluster” websocket streams, and so for now only one process will be used in handling those loads. There is a work around that would require additional configuration.  You can setup a separate config.lua file that uses different listening ports and essentially load balance between the two (or more) processes.  Certainly we understand that is not ideal, but is all we can offer at this time.

Is there any ETA on when that will be fixed? Also, might want to post that info somewhere because one of the selling points for me was the multi process non Java setup EMS has. 

Also to clarify, will running more than one config on a single server cost additional license fees?