There is no simple solution for this, and we have to solve it case by case. JDBC connection problems usually occur at runtime when an application attempts to connect to the database and perform SQL queries. This raises the number of connections and increases Oracle BI Server memory usage. Setting it to 0 enables the pool maintenance thread to clean up all of the connections in the pool after they are unused for more than the Unused Timeout number of his comment is here
Not only can it recover them, but also generate a stack trace for the code which opened these resources and never closed them. When the JVM performs GC execution of code within Tomcat freezes. The longer that a connection remains in the pool, the more susceptible it is to becoming stale. Use the removeAbandonedTimeout attribute to set the number of seconds a database connection has been idle before it is considered abandoned. my review here
Finally, if none of the previous troubleshooting steps helped to resolve the problem, continue to the MustGather for connection pooling problems. Hmm, I don't think this is really needed if you sort out your TNSNames - but I'm not an Oracle DBA :-) Common Problems Here are some common problems encountered with In addition, you can use WebSphere Application Server tracing to identify connection leaks. See "About Specifying a SQL Bypass Database" for more information.
Set to -1 to wait indefinitely. -->