Page 1 of 1

getting random errors while using PM API under low traffic

Posted: Thu May 03, 2018 4:50 pm
by needsupport22
About that specific SSL error #10053:
Question/Problem: WSAECONNABORTED (10053) Software caused connection abort.
Answer/Solution: A connection abort was caused internal to your host machine.
The software caused a connection abort because there is no space on the
socket's queue and the socket cannot receive further connections.

Any idea how we can fix this?

Re: getting random errors while using PM API under low traff

Posted: Thu May 03, 2018 5:40 pm
by Kent Briggs
So you're seeing these errors on client side when attempting an API call? Does the poker server record any errors? Is there any problem with players connecting to the server? Players and API calls all use the same file port. The "no space on the socket's queue" message sounds like a out-of-memory condition of some sort.

Re: getting random errors while using PM API under low traff

Posted: Fri May 04, 2018 12:50 pm
by needsupport22
We found the issue, PM was receiving a lot of consistant API requests from a feature we implemented, it simply cannot handle this we will move to become independant of the unreliable software in the future so we can focus on proper scaling.