Networking · interview question
In a high-concurrency environment, what is a potential risk of not setting timeouts for HTTP requests?
Multiple choiceHardchapter-11-curatedpremiumnetworkingtimeouts-and-retries
Answer and explanation
Correct answer
D. Exhausting the thread pool, leading to application unresponsiveness.
Why
Without proper timeouts, threads handling HTTP requests can hang indefinitely if the server is unresponsive, potentially exhausting thread pool resources. This can lead to application unresponsiveness as no threads are available to handle new tasks.
Test yourself on Networking
A free test with instant, explained results. No account needed.
More Networking questions
- In Java socket programming, what is the role of a two-way communication endpoint?
- Why does a Socket in Java networking matter in practice?
- When using Jackson's ObjectMapper to deserialize JSON, how can you handle unknown JSON properties without throwing an…
- Why do teams use Jackson's ObjectMapper in a Java application in production code?
- Why does the Content-Type header in HTTP requests matter in practice?
- Why can not properly configuring HTTP timeouts become a problem in practice?