#1 2022-12-02 07:35:33

dcoun
Member
From: Crete, Greece
Registered: 2020-02-18
Posts: 430

THttpClientSocket.SockRecvLn error 10053

Using THttpClientSocket to an interface service, I am getting the following in the log, but nothing is catch in except sections in my program, nor any unexpected attitude is trapped from my program.
Is it an internal http error that it is trapped and retried transparently to my code? if so, how can I exclude it from the logs?
Thank you in advance

20221202 07020721 EXC   ENetSock {Message:"THttpClientSocket.SockRecvLn error 10053 after 0 chars"} [xxdv0 BgdTmr] at 3be6e5 
20221202 07042923 EXC   ENetSock {Message:"THttpClientSocket.SockRecvLn error 10053 after 0 chars"} [xxdv0 BgdTmr] at 3be6e5

Offline

#2 2022-12-02 08:03:55

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,655
Website

Re: THttpClientSocket.SockRecvLn error 10053

IIRC on client side, those exceptions are catched internally, and the client socket is recreated, and the request tried again once.

Try to find the cause of the socket issue first.

Online

#3 2022-12-03 07:31:39

dcoun
Member
From: Crete, Greece
Registered: 2020-02-18
Posts: 430

Re: THttpClientSocket.SockRecvLn error 10053

You had right, I tried to find out what caused this error and I found it:
I had a THttpClientSocket object with an unauthorized interface service to create a JWT when needed without destroying and recreating the service interface. If more than 65 secs passed without using it and a request is done after that, using it, the above exception is created.

Offline

Board footer

Powered by FluxBB