EMS server reports ERROR: Select() failed: 10055 (Not enough buffers available, too many connections) for approximately 64 connections
Article ID: KB0086245
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
= = = = = = =
ERROR: Select() failed: 10055 (Not enough buffers available, too many connections)
Environment:
= = = = = = =
Windows
Resolution:
= = = = = =
Berkeley description: An operation on a socket or pipe was not performed because the system lacked sufficient buffer space or because a queue was full.
WinSock description: Same as Berkeley. The WinSock implementation was unable to allocate additional memory to accommodate the function request.
User suggestions: This error indicates a shortage of resources on your system. It can occur if you are trying to run too many applications (of any kind) simultaneously on your machine. If this tends to occur after running certain applications for a while, it might be a symptom of an application that does not return system resources (such as memory) properly. It may also indicate you are not closing the applications properly. If it persists, exit Windows or reboot your machine to remedy the problem. You can monitor available memory with Program Manager's "Help/About..." command.
Corrupted Winsock setting or corrupted system files such as wsock32.dll may cause this problem. Also seen due to improperly removed Layered Service Provider (LSP). This issue can be addressed by using the lspfix tool. For more detail on lspfix please search Microsoft’s web site.
If you can not identify any resource issue/application problems, and lspfix does not help it is recommended to contact Microsoft Support to further investigate this problem.
Keywords/Tags:
= = = = = = = = =
10055 select
Description:
= = = = = = =
ERROR: Select() failed: 10055 (Not enough buffers available, too many connections)
Environment:
= = = = = = =
Windows
Resolution:
= = = = = =
Berkeley description: An operation on a socket or pipe was not performed because the system lacked sufficient buffer space or because a queue was full.
WinSock description: Same as Berkeley. The WinSock implementation was unable to allocate additional memory to accommodate the function request.
User suggestions: This error indicates a shortage of resources on your system. It can occur if you are trying to run too many applications (of any kind) simultaneously on your machine. If this tends to occur after running certain applications for a while, it might be a symptom of an application that does not return system resources (such as memory) properly. It may also indicate you are not closing the applications properly. If it persists, exit Windows or reboot your machine to remedy the problem. You can monitor available memory with Program Manager's "Help/About..." command.
Corrupted Winsock setting or corrupted system files such as wsock32.dll may cause this problem. Also seen due to improperly removed Layered Service Provider (LSP). This issue can be addressed by using the lspfix tool. For more detail on lspfix please search Microsoft’s web site.
If you can not identify any resource issue/application problems, and lspfix does not help it is recommended to contact Microsoft Support to further investigate this problem.
Keywords/Tags:
= = = = = = = = =
10055 select
Issue/Introduction
EMS server reports ERROR: Select() failed: 10055 (Not enough buffers available, too many connections) for approximately 64 connections
Feedback
Yes
No
Powered by
