Dušan Panić
Dušan Panić
Python3, pooling ``` DEBUG:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 192.168.86.253 DEBUG:requests.packages.urllib3.connectionpool:http://192.168.86.253:45623 "GET /socket.io/?EIO=3&transport=polling&t=1529569781045-0 HTTP/1.1" 200 100 Traceback (most recent call last): File "testsocket.py", line 34, in ref_socket = SocketIO('http://192.168.86.253', 45623, LoggingNamespace,...
Python3, websocket ``` DEBUG:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 192.168.86.253 DEBUG:requests.packages.urllib3.connectionpool:http://192.168.86.253:45623 "GET /socket.io/?EIO=3&transport=polling&t=1529569862759-0 HTTP/1.1" 400 None WARNING:socketIO-client:192.168.86.253:45623/socket.io [engine.io waiting for connection] unexpected status code (400 {"code":0,"message":"Transport unknown"}) DEBUG:requests.packages.urllib3.connectionpool:http://192.168.86.253:45623 "GET /socket.io/?EIO=3&transport=polling&t=1529569864025-0 HTTP/1.1"...
I'll test and let you know
Hey @jupe . I have tested and here is what I know after testing. Python2 and Python3 with branch socketio-2.0 works properly ONLY if server is started in single process...
If I start cluster with 2 workers. Than all works. 3,4,5...sometimes works, sometimes not. So this is race condition somewhere in NodeJS http/https and/or socket.io, now question is where.
@jupe yes. I use it on production server for 1+ year...all works good
@jupe should we pass information to guys who made fork about cluster/non-cluster mode?
Sticky load balancing is using 'websockets' as transport, nothing more. This is error: WARNING:socketIO-client:127.0.0.1:18765/socket.io [engine.io waiting for connection] unexpected status code (400 {"code":0,"message":"Transport unknown"}) What is meaning of "properly configured...
So, here is the thing. If I select sticky routing in Socket.IO on server side, NodeJS side. Than Python client side is sending for some reason 'XHR-POOLING'. 1. If it...