getting error in websocket

pt4rh3

when i start the web socket it works for few minutes and

then i get following error

Error info: [WinError 10054] An existing connection was forcibly closed by the remote host
[WinError 10054] An existing connection was forcibly closed by the remote host

how to resolve this?

pt4rh3

@pt4rh3 @admin @rajanprabu

admin

HI @pt4rh3 Our team is working on this.We will update once this is resolved.

Surya 1

@pt4rh3

Please share your code that access the web sockets. Its hard to debug otherwise.

pt4rh3

@rajanprabu I don't think there is anything to debug, websocket works fine for few minutes and then error occurs

I have tried this in flask app
As well as tried running a single script
Both time the error happens

So the issue is at APIs end.

In upgraded version of websocket there is no option to make it threaded, why?

Surya 1

@pt4rh3

@pt4rh3 said in getting error in websocket:

So the issue is at APIs end.
In upgraded version of websocket there is no option to make it threaded, why?

I don't work for Angel, Im also a user like you. I thought you tagged me to get some help with code, hence asked. Good luck.

nahas_n

@pt4rh is this error obtained while u connecting to ur flask server or .. ?
put ss.connect() in while True loop. their webscoket connection is disconnected somehwhere around 1500 tick streaming. if its disconnected then u need to ss.connect(). .
i have over come this problem by this. and websocket connection to angel is running on separate thread . and tick accessing with queue and processing.

Surya 1

@nahas_n

then Heartbeat is also running in the same thread right ? Making threaded=True makes so much issues, mainly because Heartbeat is also started as thread inside that thread.

nahas_n

@rajanprabu their library is painful .

def connect_ws ():
    while True:
        ss.connect()

use like this instead of

 thread.start_new_thread(connect_ws, ())

if u dont have any other things going on . just call connect function in a while loop . the problem getting solved.

pt4rh3

@nahas_n error occurs after streaming some ticks

pt4rh3

@nahas_n connect_ws is not predefined method, right?

Surya 1

@nahas_n

I made a dirty trick of switching off the Signal Handlers even when its not threaded ( before line number 233 in websocket.py )

opts["installSignalHandlers"] = False

@nahas_n said in getting error in websocket:

thread.start_new_thread(connect_ws, ())

Thanks for the suggestion. I will try it out.