WEBLOGIC INACTIVE CONNECTIONS

最新推荐文章于 2023-12-12 17:08:30 发布

yyecat

最新推荐文章于 2023-12-12 17:08:30 发布

阅读量1.3k

点赞数

CC 4.0 BY-SA版权

文章标签： weblogic application components server ejb

本文链接：https://blog.youkuaiyun.com/yecat_10/article/details/5768805

本文深入探讨了WebLogic Server中连接泄漏的原因及预防策略，详细阐述了故障应用组件未能正确关闭连接导致的连接池资源耗尽问题，并介绍了WebLogic Server提供的两种机制来防止此类情况发生。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

InactiveConnectionTime
outSeconds
The number of seconds of inactivity after which reserved connections will be forcibly returned
to the connection pool.

When set to 0 (the default), the feature is disabled.
Admin Console field label:
Inactive Connection Timeout
Units: seconds
Default: 0
Minimum: 0
Maximum: 231-1

Detecting Connection Leaks
Connection leaks result from faulty application components, such as an Enterprise Javabean
(EJB), not doing their job to close a connection after using them. As stated in the J2EE Connector
Specification, Version 1.0 Final Release, once the application component has completed its use
of the EIS connection, it sends a close connection request. At this point, WebLogic Server is
responsible for any necessary cleanup and making the connection available for a future
connection request. However, if the application component fails to close the connection, the
connection pool can be exhausted of its available connections, and future connection requests can
therefore fail.
WebLogic Server provides two mechanisms for preventing this scenario: