It appears Unirest does not expose the connectionRequestTimeout when asking for connection from a pool and defaults to socket timeout . This is confusing as the potential timeout issues that are caused because of connectionRequestTimeout are solved by increasing the socketTimeout.
Further, if there are a many requests in the queue, they start timing out even if the client wants to throttle the messages and process them at a controlled rate by increasing connectionRequestTimeout while keeping the connectionTimeOut and socketTimeout the default
It appears Unirest does not expose the connectionRequestTimeout when asking for connection from a pool and defaults to socket timeout . This is confusing as the potential timeout issues that are caused because of connectionRequestTimeout are solved by increasing the socketTimeout.
Further, if there are a many requests in the queue, they start timing out even if the client wants to throttle the messages and process them at a controlled rate by increasing connectionRequestTimeout while keeping the connectionTimeOut and socketTimeout the default