It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787

question asked: Nov 23 '16, 5:22 a.m.
question was seen: 1,448 times
last updated: Nov 28 '16, 10:08 p.m.

Related questions

FAQ - How this Forum works

No buffer space available

0
han huynh (19●2●14) | asked Nov 23 '16, 5:22 a.m.
edited Nov 23 '16, 5:47 a.m.
Hi All,
I`m getting this error from server: 
Root exception is java.net.SocketException: No buffer space available (maximum connections reached?)
I read this article https://jazz.net/forum/questions/129524/no-buffer-space-available but i`m using RTC API version 6.0.1 with Windows Server 2012. Does Windows Server 2012 also have the same bug ?

Comments
han huynh commented Nov 23 '16, 10:11 p.m.

Any one can help? It's urgent for us now.

Thanks so much in advance.

One answer

Most liked answers ↓|Newest answers|Oldest answers

0
permanent link
Donald Nong (14.5k●4●14) | answered Nov 23 '16, 10:19 p.m.
There are more than one reasons that this error can appear. As I suggested in the other post, you should investigate further and gather more information about the issue. For example, is it possible that the application itself opens too many connections? The below technote lists quite a few possible causes.
http://www-01.ibm.com/support/docview.wss?uid=swg21690707

P.S. Others do have the same error with Windows Server 2012.
http://stackoverflow.com/questions/38960524/windows-2012-java-net-socketexception-no-buffer-space-available-maximum-connec
Comments
han huynh commented Nov 28 '16, 10:08 p.m.

Thanks Donald for the info.
We just need to do a simple case with calling RTC via its SDK to initial repo and always generate more 2 ephemeral ports, and take long time to release or can't release. This causes the problem of exceeding ports be provided by Window OS when having many threads run and ports can't be released.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.