All Pooled Connections in Use

  • 16 November 2022
  • 1 reply

  • New Participant
  • 0 replies

Something seems off with the API as of recently as our systems experienced a surge in user-engagement. The error is a 500 error, so I assume this is something the Copper Team may need to look into: :{"success":false,"status":500,"message":"could not obtain a connection from the pool within 5.000 seconds (waited 5.003 seconds); all pooled connections were in use"} 

We are not receiving any 425 errors, so we aren’t superseding the request cap.

Anyone have a solution for this? This issue is causing a detrimental user-experience for our supporters.



Best answer by Michelle from Copper 17 November 2022, 16:47

View original

1 reply

Userlevel 7
Badge +7

Hi @ARPA, thanks for posting! This is something I’d like to get the technical team to look at. I’ll submit a ticket for you. You’ll get an email from our system shortly, followed by a response from one of our folks. They’ll be in a better position to help you investigate.


Update: we had a surge in API traffic. Our engineers have confirmed that things should be back to normal, but please let us know if you notice any issues again. Thank you!