This content has been marked as final. Show 1 reply
There are a number of potential reasons for the error.
1) Do you have a lot of long running SQL statements that perhaps need optimisation?
To look at this, you'd need to turn on the JDBC debugging, to show the sql statements.
DebugJDBCSQL (scope weblogic.jdbc.sql) - prints information about all JDBC methods invoked, including their arguments and return values, and thrown exceptions.
2) Is the Database overloaded and slow in processing the requests?
I'd speak to your DBA about this.
3) Is weblogic perhaps overloaded - have you taken thread dumps or look at CPU/memory allocations?
4) Have you a leak in the code, that is not returning the connections to the pool?
would be useful here.