It's all about the answers!

Ask a question

No buffer space available


Felipe Hernandez (3031116) | asked Oct 03 '13, 1:43 p.m.
 Hi All,

I'm getting this error at the server.

java.net.SocketException: No buffer space available (maximum connections reached?): connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:529)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:564)
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:333)
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:123)
        at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:147)
        at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:108)
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554)
        at net.jazz.oslc.utils.HttpUtils.sendGetForSecureDocument(HttpUtils.java:144)
        at net.jazz.oslc.consumer.client.CMClientDemo.getWorkItems(CMClientDemo.java:111)

I've found one post talking about it but there's no solution posted, anyone knows how this could be solved?

The setup that we have is:
  • Windows Server 2008 Enterprise 64-bit
  • MS SQL Server 2008 R2
  • Tomcat
  • CLM 4.0.4
  • 15 Gb Ram
  • 3 CPUs 2.26 GHz
  • Virtualized environment
Regards,
Felipe A. Hernandez. 

Comments
1
Donald Nong commented Oct 04 '13, 12:57 a.m.

You need to gather more information to determine what the problem is. The error message simply says you have run out of connections. When the problem happens, use "netstat" to show all the connections and count how many of them are connected to the Tomcat server. This should give you an idea which number you should look at in the configuration file.
If you just want to play around without waiting for the problem to happen. Check the Tomcat document and examine the parameters maxConnections and maxThreads .
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html

Accepted answer


permanent link
Karl Weinert (2.0k52736) | answered Oct 04 '13, 11:00 a.m.
JAZZ DEVELOPER
Looks like it may be related to a Microsoft Windows Server 2008 R2 or Windows 7 defect

Kernel sockets leak on a multiprocessor computer that is running Windows Server 2008 R2 or Windows 7
http://support.microsoft.com/kb/2577795

Felipe Hernandez selected this answer as the correct answer

Your answer


Register or to post your answer.