WEBLOGIC INACTIVE CONNECTIONS

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: