Volley: [5311] NetworkUtility.logSlowRequests: HTTP response for request=<[ ] about volley HOT 3 CLOSED

Sorry you're having trouble!

Volley is more or less just a thin wrapper around the classes which perform the actual HTTP request. Since you're using the default HTTP stack, that would be HttpURLConnection (unless you're running on a Froyo device or older for some reason), which is built into the Android platform.

I'd recommend trying to make the same requests using HttpURLConnection directly. If you see similar slow requests - which I believe is very likely to be the case - then there's not much that can be done in Volley about it. Perhaps the device's network connection is slow. You could also try another HttpStack instead of the default - Volley has an optional one based on Cronet, and there are many floating around the web based on OkHttp - to see if it performs better. But if a simple request to google.com is taking upwards of 6 seconds, as the logSlowRequests warning suggests, then I see no reason to believe it would be significantly better with any other HTTP library.

If for some reason you can consistently reproduce this with Volley but not HttpURLConnection, please reopen with more details. (Note that the log message is just a warning logged whenever a request is taking a while; HttpURLConnection won't do this, so you should track how long the requests are taking manually).

from volley.

Still I'm Facing Same Issue

from volley.

(More details in #444 - you can add further comments here rather than opening new issues)

One thing to note is that when this warning is logged, the requests are actually failing once (presumably a timeout) and then succeeding on the second try, since retryCount = 1. This is a little strange, in that if you're setting the timeout to 30000ms, it would seem it shouldn't be failing so quickly, although timeouts are a bit strange with HttpURLConnection and don't always work as you'd expect. Are you setting any timeouts on the HttpURLConnection? What happens if you do setConnectTimeout(30000) and setReadTimeout(30000) on the connection to match what Volley is doing with your retry policy?

It might also help to enable debug logging by running adb shell setprop log.tag.Volley VERBOSE and then force-stopping/restarting your app. This should add adb logging indicating each part of the request lifecycle, including any intermediate failures.

from volley.