看了下 hibernate 应该没有限制,估计还是数据库原因导致 建立不了连接, 有个老外在介绍MySQL时候好像带到了这个错误,他说是什么,甚至给出了解决方法如果client-side 瞬间端口 无法建立,就会抛出像我一样的错误。无法理解我汗。我引用进来 大家帮忙看看One error message I'm proud of in Connector/J is the one that you get when the connection to the database is lost, or can't be made in the first place. The driver knows the various kinds of exceptions that can happen at connect-time (connection refused, bind refused, etc.) and how long it's been since the driver has (ever) communicated with the server. Based on this information it presents different kinds of error messages, and even points to solutions. For example, if there are no client-side ephemeral ports to bind to, the user gets an error message like this:"The driver was unable to create a connection due to an inability to establish the client portion of a socket. This is usually caused by a limit on the number of sockets imposed by the operating system. This limit is usually configurable. For Unix-based platforms, see the manual page for the 'ulimit' command. Kernel or system configuration may also be required. For Windows-based platforms, see Microsoft Knowledge Base Article 196271 (Q196271)." 还是找不到,难道还是数据库的问题吗?
hibernate不是有事务吗?还要自己建connection
3楼,能具体一点吗?增大socket连接数。难道是hibernate的开发包限制了 socket连接数?
我找找看原因,谢谢 3 楼 5楼
有个老外在介绍MySQL时候好像带到了这个错误,他说是什么,甚至给出了解决方法如果client-side 瞬间端口 无法建立,就会抛出像我一样的错误。无法理解我汗。我引用进来 大家帮忙看看One error message I'm proud of in Connector/J is the one that you get when the connection to the database is lost, or can't be made in the first place. The driver knows the various kinds of exceptions that can happen at connect-time (connection refused, bind refused, etc.) and how long it's been since the driver has (ever) communicated with the server. Based on this information it presents different kinds of error messages, and even points to solutions. For example, if there are no client-side ephemeral ports to bind to, the user gets an error message like this:"The driver was unable to create a connection due to an inability to establish the client portion of a socket. This is usually caused by a limit on the number of sockets imposed by the operating system. This limit is usually configurable. For Unix-based platforms, see the manual page for the 'ulimit' command. Kernel or system configuration may also be required. For Windows-based platforms, see Microsoft Knowledge Base Article 196271 (Q196271)."
还是找不到,难道还是数据库的问题吗?
这个老外说的也正确,还带点原理。
http://support.microsoft.com/kb/196271