Java SocketServer is not limited by backlog value


Question


I'm using client-server mechanism inside my app to transport internal data. One of server parts should be designed to serve one request at time, no threads, no backlogs. I found weird functionality then using:

serverport = new ServerSocket(port, 1, InetAddress.getLoopbackAddress());

This one continue to receive incoming connection even after one is already backlogged? Any suggestions how it's possible, and how may I workaround the issue?


Answer 1:


As it says in the Javadoc:

The backlog argument is the requested maximum number of pending connections on the socket. Its exact semantics are implementation specific. In particular, an implementation may impose a maximum length or may choose to ignore the parameter altogther. The value provided should be greater than 0. If it is less than or equal to 0, then an implementation specific default will be used.



来源:https://stackoverflow.com/questions/32885119/java-socketserver-is-not-limited-by-backlog-value


码神部落- 版权声明 1、本主题所有言论和图片纯属会员个人意见,与码神部落立场无关。
2、本站所有主题由该帖子作者发表,该帖子作者半岛情歌码神部落享有帖子相关版权。
3、码神部落管理员和版主有权不事先通知发贴者而删除本文。
4、其他单位或个人使用、转载或引用本文时必须同时征得该帖子作者半岛情歌码神部落的同意。
5、帖子作者须承担一切因本文发表而直接或间接导致的民事或刑事法律责任。
6、本帖部分内容转载自其它媒体,但并不代表本站赞同其观点和对其真实性负责。
7、如本帖侵犯到任何版权问题,请立即告知本站,本站将及时予与删除并致以最深的歉意。

最新回复 (0)
    • 码神部落
      2
        立即登录 立即注册 GitHub登录
返回
发新帖
作者最近主题: