Problem Description
From the weblogic console, you can see that the connection leak has reached 6K+, and the application has become very unstable.
According to past experience, the leakage of the connection pool is generally caused by the code applying for a database connection, which is not closed normally after use, resulting in the connection being consistently occupied. After the application runs for a long time, more and more leaked connections accumulate, causing the application When connecting to the database, there is no available connection, so the application reports an exception.
Troubleshooting process
From PLSQL tools-session
1. Check the Weblogic console and find that the available quantity is 0
2. Check the log, report an error, and cannot get the connection
Connection has been administratively destroyed because the pool got too many consecutive failed connection tests, and failures to obtain replacement connections from the DBMS. Please see the server log entries at that time for more details. Reconnect. java.lang.Exception: It was destroyed at Sat Oct 10 16:28:14 CST 2020
at weblogic.jdbc.common.internal.ConnectionEnv.destroy(C