[firebase-br] Win32 error 10055 (No buffer space available)

Otto ottofuch em terra.com.br
Qua Jun 14 15:18:59 -03 2006


Na realidade, o significado completo da mensagem é:
An operation on a socket could not be performed because the system lacked
sufficient buffer space or because a queue was full.
a) system lacked sufficient buffer space
ou
b) a queue was full

Parece tratar-se de algum problema de configuração da rede, ligado com
Winsock. Uma referência encontrada foi:

"BUG: Send() Fails with Error WSAENOBUFS Over Blocking Socket
----------------------------------------------------------------------------
----
The information in this article applies to:
Microsoft Windows NT 4.0
Microsoft Windows versions 95, 98
----------------------------------------------------------------------------
----

SYMPTOMS
When large blocks of data (for example, 3-4 MB) are sent over a blocking
socket, send eventually fails with error 10055, WSAENOBUFS.

The online documentation indicates that send over a blocking socket should
block if there is no system buffer space available:

If no buffer space is available within the transport system to hold the data
to be transmitted, send will block unless the socket has been placed in a
nonblocking mode. On nonblocking stream oriented sockets, the number of
bytes written can be between 1 and the requested length, depending on buffer
availability on both client and server machines.

RESOLUTION
When you encounter the problem described in the "Symptoms" section, please
consider using one of the following workarounds:

Use the socket in nonblocking or asynchronous mode.

Break large-size data blocks into small ones and specify a relatively small
buffer in send for blocking sockets, preferably no larger than 64K.

Set the SO_SNDBUF socket option to 0 (zero) to allow the stack to send from
your application buffer directly.

STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at
the beginning of this article.

Additional query words:

Keywords : kbNTOS400bug kbSDKPlatform kbWinOS95bug kbWinOS98bug kbWinsock
kbDSupport kbGrpNet
Version : WINDOWS:95,98; winnt:4.0
Platform : WINDOWS winnt
Issue type : kbbug
Technology :
Last Reviewed: November 30, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use. "

Não sei se atrapalhei.
[]´s
Otto





----- Original Message ----- 
From: "Jeferson Oliveira" <jefersonfoliveira em gmail.com>
To: "FireBase" <lista em firebase.com.br>
Sent: Wednesday, June 14, 2006 2:59 PM
Subject: [firebase-br] Win32 error 10055 (No buffer space available)


Caros colegas,

Ao tentar estabelecer conexão com um banco de dados local, após formatação e
reinstalação do sistema operacional, recebo a seguinte mensagem de erro:
"Unable to complete network request to host: "NomeHost".
 Failed to stablish a connection.
 unknown Win32 error 10055"
Segundo a lista de erros de Winsock disponível no site da Microsoft
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/wi
nsock/windows_sockets_error_codes_2.asp
) o erro 10055 significa "No buffer space available". Não entendi o que isso
significa propriamente. A que buffer a mensagem se refere?

Configurações:
 Aplicação: Delphi + IBX
Servidor Fb: 1.5 SuperServer
S.O.: Windows XP Professionnal SP2
Sistema de arquivos: NTFS

Qualquer sugestão para correção desse problema será muito benvinda.


Abraço!
Jeferson Oliveira
______________________________________________
FireBase-BR (www.firebase.com.br) - Hospedado em www.locador.com.br
Para editar sua configuração na lista, use o endereço
http://mail.firebase.com.br/mailman/listinfo/lista_firebase.com.br
Para consultar mensagens antigas: http://firebase.com.br/pesquisa







Mais detalhes sobre a lista de discussão lista