oracle 带有 JNDI 数据源的 Weblogic ResourceLimitException
声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow
原文地址: http://stackoverflow.com/questions/21638404/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Weblogic ResourceLimitException with JNDI data-source
提问by Chaitanya
I have deployed a third party web-application onto my Weblogic server and this application connects to Oracle Database using JNDI data-source that I have defined in my weblogic server. Now while I use the web-application, I don't see any issues, and after accessing the application for a while it throws an exception as below-
我已将第三方 Web 应用程序部署到我的 Weblogic 服务器上,并且该应用程序使用我在 Weblogic 服务器中定义的 JNDI 数据源连接到 Oracle 数据库。现在,当我使用 Web 应用程序时,我没有看到任何问题,并且在访问该应用程序一段时间后它会引发如下异常-
weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool test_db to allocate to applications, please increase the size of the pool and retry.. caused by: weblogic.jdbc.extensions.PoolLimitSQLException:
How can I debug this issue using my weblogic server? Is there any log file that contains details on why all the connections are still used?
如何使用我的 weblogic 服务器调试这个问题?是否有任何日志文件包含有关为什么仍然使用所有连接的详细信息?
回答by AnBisw
Steps:
脚步:
- Go to WLS Console
- Select Services -> Datasources -> select the datasource you want to change the pool size
- Go to Configuration -> connection pool
- Change the Maximum Capacity to the count which is required for your application.
- 转到 WLS 控制台
- 选择服务 -> 数据源 -> 选择要更改池大小的数据源
- 转到配置-> 连接池
- 将最大容量更改为您的应用程序所需的计数。
回答by Awa
I had the same problem. You can see this : http://www.albinsblog.com/2012/10/resourcelimitexception-no-resources.html#.VqX7-U_YRnm
我有同样的问题。你可以看到这个:http: //www.albinsblog.com/2012/10/resourcelimitexception-no-resources.html#.VqX7-U_YRnm
The problem is there was too much waiting for connection to JDBC Datasource. For this, I increased the number of connections in the connection pool, like the recommandations in the link.
问题是等待连接到 JDBC 数据源的时间过长。为此,我增加了连接池中的连接数,就像链接中的建议一样。