Your development team has written an application using the C language sockets API

Your development team has written an application using the C language sockets API. Your team has written both the server and client. The code always compiles correctly and runs correctly sometimes (e.g., runs for several hours without trouble). However, at other times the (same, unmodified) server blocks forever on a read ( ) call. The read ( ) does not return an error. Your server does not exit. The server just blocks forever on the read ( ). 
(a) Give one significant and possible explanation for this behavior. Consider aspects of client-server systems, the C language sockets API, server architectures, and application protocols. Briefly but carefully, explain your answer. 
(b) For your theory for this behavior, what do you recommend as the fix or solution to the problem given in (a)? Briefly but carefully, explain your answer. 
Be sure to explain why the error occurs sometimes, but not all the time. Note that this question is not about C programming. Therefore, the bug is not a buffer overflow nor a wild pointer write. The details of the parameters to read ( ) are not relevant to the question.