Error when two requests are too close in time #367
-
Hi, I'm getting this error when I make a request close after another (not always, it's a range, not inmediate and not long after it):
From what I read this happens when using the BasicHttpClientConnectionManager and having more than one request open, depending on timing it will reuse the connection on create a new one. Is there a way to avoid this (I may be using the API wrong)? Right now I have a wrokaround with a wrapper that catches the exception and retries, but asking in case there's a better way to handle this. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
You're on the right track. You can try to use a pooling connection manager as |
Beta Was this translation helpful? Give feedback.
You're on the right track. You can try to use a pooling connection manager as
httpManager
by building a custom SpotifyApi instance.