James
James
from your log, the reason is the websocket pipe between janus proxy and your client is broken which results into exception when we send mesage to it. janus-proxy has catch...
For some high work load case, it's possible that the low level socket may be already broken but the high level business is not yet notified about that and still...
I think this log **is not** the real reason make you failed, please check the cpu workload of janus-proxy
I think this problem may be in your front http(websocket) proxy . the ws connections from the http proxy (like 127.0.0.1:46960) to the janus-proxy(maybe 127.0.0.1:8288) broken for some reason. Please...
maybe the file fd number limitation? please check ulimite -a also
from the error infomation, the filename, which you provice in "publish" request, contains some special char like @, which cannot be used as filename on linux. Please give the params...
the publish param means the websocket reqeust(json format) which is sent by (web)client to janus-proxy. NOT the configuration file of some server
multi janus-cloud is a complecated issue which means the video room status must be share and triggered by multi janus-proxy, maybe make use of zookeeper is a good idea. But...
multistream API support is coming!!!