Kbase P118200: Java socket error "No buffer space available" in the WebSpeed broker log filewhen the port being use
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/09/2008 |
|
Status: Verified
SYMPTOM(s):
Java socket error "No buffer space available" in the WebSpeed broker log filewhen the port being used exceeds 5000 range in Windows
Error creating private listening socket: java.net.SocketException:No buffer space available (maximum connections reached?): listen failed
Unhandled exception caught in <threadName>. (8419)
The java NullPointerException is followed by the above error:
java.lang.NullPointerException
at com.progress.ubroker.broker.ubWSserverThread.bldCmdLine(ubWSserverThread.java:223)
at com.progress.ubroker.broker.ubServerThread.startServer(ubServerThread.java:1169)
at com.progress.ubroker.broker.ubServerThread.processStartup(ubServerThread.java:1755)
at com.progress.ubroker.broker.ubWSserverThread.processStartup(ubWSserverThread.java:271)
at com.progress.ubroker.broker.ubServerThread.processEvent(ubServerThread.java:1003)
at com.progress.ubroker.broker.ubServerThread.mainline(ubServerThread.java:414)
at com.progress.ubroker.broker.ubServerThread.run(ubServerThread.java:323)
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
Progress 9.1x
OpenEdge 10.x
The error is apparent when additional agents are being spawned by the broker
The WebSpeed broker crashes after the error
The WebSpeed broker is set to run on port higher then 5000
CAUSE:
This is a Microsoft bug. The cause written on the Microsoft article 196271 as
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
FIX:
There are two workarounds:
1. Use broker port less then 5000
Or,
2. Follow the Microsoft article to fix the port range in the registry:
When you try to connect from TCP ports greater than 5000 you receive the error 'WSAENOBUFS (10055)'