Posted by Erland Sommarskog on 10/01/22 11:19

(daniel.shaya@tamesis.com) writes:
> I'll try and keep this brief so in a nutshell:
>
> I have large distributed java system running on a Windows 2003 server
> (4cpu 8Gb memory).
>
> Periodically the following exceptions occurs in the servers:
>
> java.net.SocketException: No buffer space available (maximum
> connections reached?): recv failed
>
> I know for a fact we are not using too many TCPIP sockets or running
> too many socket servers.
>
> I have googled this error and found very little to help me.
>
> What buffer space is this?
> What does recv failed mean?
>
> (Is it at all relevant that sql server is running on the same box?)

At least I can answer the question what "recv failed". It means that a
call to recv failed. recv is one of the basic TCP/IP functions. Doing
"man recv" on a Unix box, I see

recv, recvfrom, recvmsg - receive a message from a socket

As for the buffer space, I assume that there is a shortage of
virtual memory somewhere. Maybe because you are not closing connection
correcly, or retrieving all data. Or you simply have a memory leak.
But I don't know Java, so I don't really have a clue in that part.

Whether the presence of SQL Server could matter, SQL Server by default
grabs as much memory it can, so it can as much in cache as possible. Then
again, it yields memory if another app competes for memory. You could
configure SQL Server to use less memory, but my gut feeling tells me
that you would still see this message, just less often.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

[Back to original message]