Open source software supply chain lighting plan, waiting for you>>>
Error in starting project B: java.net.socketexception: no buffer space available
First, the maximum number of connections in MySQL is changed from 100 to 500. After restarting mysql, the same problem is still reported, indicating that it is not caused by the maximum number of connections
Then I checked the data and found that it might be caused by insufficient memory resources of the server where project B is located. It was found that the server had only 2G of memory, and another memory hungry project a was running. When project B was not started, it consumed 1.7g of memory. So it was decided to stop project a, which occupied a lot of memory. Immediately, the memory occupation was reduced from 1.7g to 0.6g, which was enough to free 1g of memory. Sure enough, we started project B, which we had just started to report an error, and then we successfully connected to MySQL
Conclusion:
Most of the above problems are caused by insufficient memory resources in the project server. It is recommended to leave enough memory space for the project
Reference:
https://www.cnblogs.com/hjwublog/p/5114380.html
https://www.iteye.com/problems/85845
Address: https://www.cnblogs.com/poterliu/p/10948981.html
Similar Posts:
- Some solutions to the error of [the underlying provider failed on open]
- ORA-12519: TNS:no appropriate service handler f…
- LoadRunner uses HTTPS request
- [Solved] MYSQL Error 1040 (HY000): too many connections
- Mysql ERROR 1040 (HY000): Too many connections
- When hive processes data, it cannot run directly and reports an error: execution error, return code 2 from org.apache.hadoop.hive.ql.exec.mr
- [Solved] MYSQL Error: [Warning] Changed limits: max_open_files: 1024
- tomcat PermGen space
- Go error reported unimplemented: 64 bit mode not compiled in and MinGW 64 bit installation error res resolved
- Insufficient space for shared memory file [How to Solve]