SCM

[#1000483] An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

View Trackers | Bugs | Download .csv | Monitor

Date:
2005-12-14 10:53
Priority:
3
State:
Open
Submitted by:
Nobody
Assigned to:
Nobody (None)
Npgsql Version:
None
Category:
Group:
Resolution:
None
Summary:
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

Detailed description
Hi all
this is the error i've been getting really frequently, starting 3 days ago.

Exception: System.Net.Sockets.SocketException
Message: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
Source: System
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)
at Npgsql.NpgsqlClosedState.Open(NpgsqlConnector context)
at Npgsql.NpgsqlConnector.Open()
at Npgsql.NpgsqlConnectorPool.GetPooledConnector(NpgsqlConnection Connection)
at Npgsql.NpgsqlConnectorPool.RequestPooledConnectorInternal(NpgsqlConnection Connection)
at Npgsql.NpgsqlConnectorPool.RequestPooledConnector(NpgsqlConnection Connection)
at Npgsql.NpgsqlConnectorPool.RequestConnector(NpgsqlConnection Connection)
at Npgsql.NpgsqlConnection.Open()

I'm new to postgre and I really need help. According to the dbadmin at hte moment the error occures there are only 8 connections to the DB Server. And we made sure all opened connection are closed in the code.

Thank in advance
BR
Daniela

PS: we have Win 2003 Server Web edition, Linux base DB server and npgsql 0.7.0.0

Followup

Message
Date: 2008-08-11 01:16
Sender: Francisco Figueiredo jr.

Can you try again on latest Npgsql release and see if this still occurs?

Thanks in advance.
Date: 2006-07-20 23:18
Sender: Nobody

Hello,

I am getting the exact same error and I can pretty much reproduce it all the time. It happens when I try to obtain a large object that has a big filesize (example a 110meg video).
The application locks for a few seconds then gives this error.

Here's the code I use to get the large object :

NpgsqlTransaction t = connection.BeginTransaction();
LargeObjectManager lbm = new LargeObjectManager(connection);
LargeObject lo = lbm.Open(oid, LargeObjectManager.READWRITE);

byte[] buf = new byte[lo.Size()];
buf = lo.Read(lo.Size());

lo.Close();
t.Commit();
p_stream = new MemoryStream(buf);


Maybe I should get the large object in chunks instead of all at once???
Date: 2006-05-07 22:50
Sender: Josh Cooley

Since sockets are a global system resource this may or may not be an Npgsql bug. Here's a Microsoft kb article that may give you some ideas.
http://support.microsoft.com/default.aspx?scid=kb;en-us;815209

Do you have a reproducable test case? If not, does it happen on just one machine?

Thanks.

Attached Files:

Changes:

No Changes Have Been Made to This Item

Powered By FusionForge